> From: Jeff Trawick [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 06, 2003 5:50 PM
Thanks for confirmation. At least I know I'm not barking
up the wrong tree.
> We can't close the socket. Otherwise, how would we read the
> output of
> the CGI back in the child process [thread] that sends the CGI output
> back to the client?
I realize that (otherwise I'd do it myself). I was hoping for some
other
workaround.
> So use mod_cgi :)
>
> (If there isn't a compelling performance difference, that makes sense
> from Apache's perspective because mod_cgid is unfortunately
> complicated
> and it isn't worth more tricks if there's no sense in using it in the
> first place.)
My understanding of the world is that mod_cgid is necessary
for decent performance with worker threads.
Just as supporting mod_cgi.c and mod_cgid.c adds to Apache maintenance
work, for us to have to support both models would be prohibitive.
Hence my desire for a good workaround.
Gary
====================================================================
Ready-to-Run Software, Inc.
The Industry's Leading Provider of
Cross-Platform Software Services
*****************************
email: [EMAIL PROTECTED] Gary Feldman
fax : 1-978-692-5401 Ready-to-Run Software, Inc.
voice: 1-978-251-5431 11 School Street
www : http://www.rtr.com North Chelmsford, MA 01863
USA
