Hi - I read the entire thread mentioned below, and missed any mention of anyone saying the AS maintainers would not accept FastCGI.
The other thing I guess I'm confused about, is that CGI is implemented as an AS module. Why can't someone write a FastCGI module, and whoever wants it can load it to get FCGI support? Does the core have to be modified to support FastCGI? And just as a "my dog isn't in this fight" observer, this discussion seems to be getting rather personal, which probably is not going to help it proceed productively. Jim > Here's the kicker: > > The guy who'd probably do most of the work, John Sequeira, seems to > think that option 1. is a better idea technically, but is leaning > towards 2. instead, because after following the AOLserver > multi-protocol discussions, he doubts that any FastCGI work would ever > be accepted by the AOLserver maintainers, no matter what! > > http://openacs.org/forums/message-view?message%5fid=263944 > > That looks symptomatic of a problem in how the AOLserver codebase is > managed to me. Dossy, doesn't it look that way to you too? > > -- > Andrew Piskorski <[EMAIL PROTECTED]> > http://www.piskorski.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
