httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From r..@covalent.net
Subject RE: Unbuffered CGI's on NT.
Date Thu, 13 Apr 2000 14:28:53 GMT

> > > > Agreed!  As long as you offer two code paths, it doesn't matter.
> > > > With adaquate warnings, we should release a stable NT 2.0, with
> > > > the Win95/98 able to serve pages.  If async CGI doesn't work on
> > > > the 95/98 family in 2.0, perhaps someone will offer the patch 
> > > > for 2.1 - let's get on with it :~)
> > > 
> > > can't you just choose a different iol at run-time?
> > 
> > That's what I did in my patch (well except we didn't have IOL's, so I
> > created a different kind of pipe at run-time).  The problem is that 95/98
> > don't allow what we need for non-blocking CGI's.  It is impossible AFAIK
> > to create a non-blocking pipe in 96/98 without async, and as has been
> > pointed out before, async I/O and the current IOL's don't play nicely
> > together yet.
> 
> um, what about my post yesterday saying to just have a second buffer in
> the iol itself for async i/o?

Great, but that takes time to code and test.  And, why do we care.  The
async is only an issue on 95/98 where IMHO, we really shouldn't care about
getting unbuffered CGI's.

Ryan

_______________________________________________________________________________
Ryan Bloom                        	rbb@apache.org
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------


Mime
View raw message