You might be able to do the same thing by using apache/mod_perl and your own custom C code. You could write the primary handler in C. If the request meets the requirements that your application has for using the Perl providers then you could perform an internal redirect to the Perl handler, get the results and then return that to the user.

This would, in my mind, simply your code greatly. You would no longer have to worry about handling multiple connections, logging, etc. You would also not have to worry about a pool of persistent Perl interpreters since your pool of apache children would be a pool of Perl interpreters.

In reply to Re: Maintaining a pool of Perl interpreters by mpeters
in thread Maintaining a pool of Perl interpreters by jredburn

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.