Well, it's possible this may not work in your particular case, but I wanted to offer this -- are you certain that you can't move your CGI script code into modules of some sort? If you were capable of doing that -- instead of using an expensive fork call, you could do a simple subroutine call, and just pass parameters that way.
Another benefit of that method is that it makes it even simpler to move to something like mod_perl. If you're calling 20 CGI programs, the cost of that could be huge.. but if they were Perl modules loaded in mod_perl, the cost of that would actually be quite negligable, aside from RAM considerations. Slashdot uses more modules then that, and they were about the only news site that survived last Tuesday :-)
If this doesn't work for you, perhaps you could give some more details about the project you are working on. Good luck!
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- 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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||