Now, mod_fastcgi handles process creation automatically, even dynamically
sizing the pool, and passing requests to individual children (using the
fastcgi protocol). This seemed to be ideal. I made a small mod to DRb so
that it does not accept() another incoming request until the current one has
completed, and hey presto.sounds really cool. how do you prompt mod_fastcgi to spwan a process? are
you hitting it via http and the web server or using it directly?
I was originally just hitting it with HTTP; mod_fastcgi spawns a variable
number of processes by default, using an algorithm which creates extra ones
and kills them off which you can tune. But now I think I prefer to have my
pool of a fixed size, so that it’s ready to respond to peak load at all
times:
FastCgiServer /var/apache/fcgi-bin/foo.cgi -processes 5
[cgi.html { nonsense }]
funny, i NEVER use this except for in my example program. i use amrita for
all my stuff.i love amrita. anyone used to new C version?
I love amrita and I haven’t even used it yet 
Just from the docs it’s
exactly what I’ve been looking for. Is C version the “unstable” one?
Cheers,
Brian.
···
On Tue, Mar 11, 2003 at 10:09:05AM +0900, ahoward wrote: