httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Bloom" <...@covalent.net>
Subject RE: 2.0.34 - erratic behavior with autoindexes
Date Wed, 03 Apr 2002 03:23:29 GMT
> >The core can't do anything about it.  If you are creating a
sub-request,
> >you must flush the data.  We could have the core always flush, but
that
> >would cause us to send flush buckets before any data has been
generated,
> >or in cases where a flush is not required.  The module MUST be the
thing
> >that does the flush.
> 
> Of course it can... why not simply have ap_run_sub_req automatically
flush
> the rwrite'n contents of the main request upon invocation, and
> automatically
> flush the rwritten contents of the subrequest upon completion?
> 
> Then all is transparent

That is what I meant by "We could have the core always flush....".  As I
said, that would mean that we are flushing when we don't need too, and
we are potentially sending small chunks of data to the socket when we
don't need to.  It is and should be up to the module to ensure that data
is sent to the client when it is supposed to be.

Ryan



Mime
View raw message