From: "A.M. Kuchling" <amk@...>
Date: 2003-02-11T02:55:24+09:00
Subject: Re: one lonely fcgi user

On Mon, 10 Feb 2003 16:23:27 +0000, 
	ahoward <ahoward@fsl.noaa.gov> wrote:
>   * best methodology for shutting down/reloading script, there seems to be too
>     many ways to put apache into a bad state using fcgi's

My project group kept running into mysterious hangs with Apache's 
mod_fastcgi, and one of us wrote a slightly different module, mod_scgi 
(http://www.mems-exchange.org/software/scgi/).  SCGI tries to keep things
simple, so Apache never starts an SCGI process for you.  Instead, you run a
separate server process that can be started and stopped independently of
Apache.  The advantages are that the mod_scgi C code is *much* simpler, the
SCGI protocol is simpler than the FastCGI protocol, and you can run the SCGI
server under any user ID and group ID you like.

Currently there's only a Python SCGI client module, but a Ruby module would
certainly be added to the distribution, if anyone wants to write one.

--amk                                                    (www.amk.ca)
I'm as fit as a trombone.
      -- The Doctor, in "Time and the Rani"