Well... you can also run a fastcgi on the command line... which we do... the problems I refer to are involved more with things like problesm with STDOUT and a strange problem where cgi-fcgi is having problems with our firewall... and packets are getting mangled... I looked at the cgi-fcgi c code... and it was awful...

End result, it is easier to rewrite FCGI in perl, which also gives us the added bonus of changing the number of availble fastcgi clients on demand, and graceful shutdowns, so they act more like apache... very nice... seems to be coming together nicely...

                - Ant
                - Some of my best work - (1 2 3)

In reply to Re: Re: IO::Select can_read missing some reads... by suaveant
in thread IO::Select can_read missing some reads... by suaveant

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.