> On Mon, 19 Aug 2002, Blaise Tarr wrote: > > > Thanks Brian. It's much better now, but it still buffers in 8K chunks > > as opposed to the 2.0.32 behavior where there was no apparent > > buffering. > > This is probably because it's doing a blocking read on the pipe bucket.
Which is the mistake. Someone removed the code I put in (probably because that did not understand what it was for?) to do non blocking reads on the CGI pipe. The code in Apache 2.0.32 was in one aspect better than what was in 1.3. If we ever received bytes on the CGI pipe in 2.0, we would set the reads back to non-blocking again (which would cause another network flush if a read returned EWOULDBLOCK). Bill
