In such a scenario, I would look at the manner by which the dispatch is ordered, seeking for any hierarchy which may be utilised to further define run-modes - I would then separate those group run-modes of similar functionality into separate dispatches. These separate dispatches could then be moved into separate scripts with a shared server-side backend where required.
If this was not possible, I would investigate the dynamic loading and unloading of module components through the use of the use and no module functions - This should allow memory to be allocated and freed as necessary but the details of whether this memory is returned to the system is dependent upon the runtime C library.
In any case, I would be incorporating the CGI::Application dispatch into the apache binary with mod_perl. Based upon the intended scope of the project described, the performance advantage of employing mod_perl cannot be ignored.
perl -le 'print+unpack("N",pack("B32","00000000000000000000001000100100"))'
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||