Lars Appel <[log in to unmask]> wrote:


> Ken was kind enough to shed light...
>
> >Initialiaze (open databases, etc)
> >loop
> >   call FCGI_accept
> >    if it returns <0, exit loop
> >    else
> >       normal CGI processing
> > endloop
>
> Any idea if the fast_cgi approach would always end up "single
> threading" the request handling? Or is there a way to allow more
> than one concurrent request being handled by the fcgi server?

You can have as many server processes as you want. You can configure
'mod_fastcgi' to spawn/kill processes depending on the load.  The
FCGI_accept call does a socket 'accept()' call, but unlike a typical unix
server process, it does not fork after accepting.   If there are multiple
processes waiting on the socket with accept() calls, MPE/iX picks the first
one to actual return the connection.  They are handled in FIFO order on
MPE/iX.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *