> Okay, time for me to step into the fray.
>
> Here's how this works:
>
No, that is how one way works...
If you run Apache using either mod_perl, pyapache(aka mod_python) or
FastCGI then the server does NOT spawn a new process for the cgi
script. It passes the request to the cgi script *which is already
running*, which then handles it (sounds familiar).
The difference between FastCGI and mod_* is that the mods expose the
apache API to interpreter be it Perl, Python, whatever.
> When a webserver (let's say Apache) gets a request from a client to run
> a traditional CGI, the server spawns a new process *independent* of
> itself. If the process is a Perl process, then it has the overhead of
> initialization, reading in the file, parsing, etc. *before* it can do
> anything useful to the end user.
>
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Tom Jenkins
DevIS
Linux & Samba 2.0 : The best Windows file server
http://www.zdnet.com/sr/stories/issue/0,4537,2196106,00.html
"Do not be overcome by evil, but overcome evil with good." Romans 12:21
