I got a similar problem. From what I have read, some are installing the new Apache 2.4 and with a redirect rule, redirecting all old perl cgi requests to the old Apache 2.2 server (but at a performance hit, due to an extra server in the chain, but this backserver does not need to serve static files anymore, so it could balance out). This way, when/if mod_perl becomes available, they can switch more easily. Of course, the old Apache only accepts incoming connections from that new Apache, thus, making it less risky (when patches stop, pun intended).

edit: Apache began as a-patchy-server (explaining the pun)

edit2: Compile ourselves: Yes, Windows world is a bit different (but tell me what to do after the nmake and I'll give it a shot): The houses that offer Apache pre-compiled still do not bundle nor offer it (I checked a few weeks ago, it could be different now).

edit3: Or you just jump the gun, hire some temporal staff to help migrate and write a wrapper for your perlscripts to accept mod_proxy_fcgi.

In reply to Re: Your wisdom on what to do with Apache 2.2 (eol) + mod_perl on Windows 64 by FreeBeerReekingMonk
in thread Your wisdom on what to do with Apache 2.2 (eol) + mod_perl on Windows 64 by RayHunter

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.