FreeLists / openbeos / [openbeos] Re: Web hosting from DreamHost, for free.

[Michael Phipps <mphipps1@xxxxxxxxxxxxxxxx>]

A normal CGI does a fork and exec() to start the CGI application.

FastCGI runs in a loop (think BLooper), waiting for requests. There is a 
thin wrapper that your CGI needs, but it is pretty trivial to change one 
into the other.
The downside of fastcgi is that if you have a memory or handle leak (db, 
ldap, whatever), code that runs in a CGI will break under load.

Charlie Clark wrote:
> Am 06.12.2006 um 20:02 schrieb Mikael Jansson:
>
> > It's a FastCGI process. Like a daemon, but fixed number of requests 
> > per "up period". Same for all my instances at http:// bits.jansson.be, 
> > so that shouldn't be the problem.
> Meaning what exactly? How many requests per "up period"? :-? Not that it 
> really matters as the best thing is not to have your application 
> interrupting your web server at all. SCGI, mod_rewrite, mod_proxy or 
> mod_python all provide alternatives.
> Charlie