Re: concurrent connections and multiple accepts

At 06:21 AM 06/16/05, you wrote:
>Hi
>
>We run an 'appserver' which is written in perl and basically fork some children and manages them.
>Each child is a FCGI application, which does
>$request = FCGI::Request(\*STDIN, \*STDOUT, \*STDERR, \%ENV, $socket, 0)
>
>and then loops on
>$request->Accept
>
>in the same way all the FCGI examples do. ...

This is the first red flag.  It seems you're doing a lot of extra work to redo the FCGI process structure incorrectly.  FCGI provides for multiple concurrent instances of the FCGI app., adding processes as load goes up and killing off extra ones when things quiet down.  So it's not clear you need the forking logic, etc. as that's what the FCGI process manager does.  Note that an FCGI can still fork its own subprocesses to handle tasks for the current invocation, but there's no need to get into managing the FCGI processes themselves.
HTH,
TW

___________________________________
fastcgi-developers mailing list
http://fastcgi.com/fastcgi-developers/