Ah well, every once in a while I have to take a stab at understanding and
stick my neck out. I re-read your original description and now understand.

And Patrick, I'd go with the 'less load on the server' argument with your
hoster. For any significant application its sure to make a big difference.
If you have a local *nix box to play on you should compare your app running
on CGI vs SCGI or some similar approach - its night and day different.

At 12:10 PM 5/29/2002 -0400, Greg Ward wrote:
>On 29 May 2002, Michael Watkins said:
> > Also, since the actual Quixote applications are not LRWP, only the single
> > generic SCGI process is (correct guys?)
>
>Sorry, wrong on both counts if I understand things correctly: if you use
>SCGI, each Quixote application runs as a separate SCGI daemon
>("long-running web process" -- I assume that's what LRWP stands for?"),
>listening to a separate TCP port for requests from the SCGI client --
>currently mod_scgi for Apache.
>
>As I see it, that's actually a huge benefit of SCGI: you get total
>separation between the web server and web application(s).  One user's
>app might run under one UID, and another user's app under a completely
>different UID.  You certainly don't get that when the web application is
>run from the HTTP server.
>
>         Greg
>
>_______________________________________________
>Quixote-users mailing list
>Quixote-users@mems-exchange.org
>http://www.mems-exchange.org/mailman/listinfo/quixote-users