On 5/20/06, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:

Am 20.05.2006 um 21:41 schrieb Stephen Deasey:

> This is almost a Fast CGI module.  Differences are this uses pipes,
> while Fast CGI uses sockets (although the code mentions a move to
> sockets).  Fast CGI produces a complete response for the browser,
> where as this returns a script result to the calling proc.  But the
> differences are small.
>
> I'm not sure 'proxy' is the best name for this, bundled with a web
> server as it is...

Well, to be honest, I also was not sure about the "proxy" name.
How would you name it?


You could call it nsfastcgi  :-)


About the resemblence to FastCGI I can't say much but this might be.
I never looked at that code. Is that something bad, I mean the
resemblence to fastcgi? BTW, where is this module?


There's no aolserver module, as far as I know, but there's been
interest.  http://fastcgi.com has details.


Noticed a couple of things in nsproxy:  the name space for Tcl handle
is global, should be per virtual server.  Could the handle code be
split out?  It's similar to the stuff in nsd/tclobj.c, although for
different situations.  Would be good as library code.

Reply via email to