Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Sender: gregames
Message-ID: <3D176BF5.5377991C@apache.org>
Date: Mon, 24 Jun 2002 14:59:01 -0400
From: Greg Ames <gregames@apache.org>
MIME-Version: 1.0
To: dev@httpd.apache.org
Subject: Re: core_output_filter buffering for keepalives?  Re: Apache
 2.0Numbers
References: 
 <Pine.LNX.4.44.0206240200060.9140-100000@deepthought.cs.virginia.edu>
 <1024902128.1576.82.camel@localhost>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Brian Pane wrote:

> The more I think about it, though, the more I like the idea of just
> writing the brigade out to the client immediately when we see EOS in
> core_ouput_filter(), even if c->keepalive is true.  If we do this,
> the only bad thing that will happen is that if a client opens a
> keepalive connection and sends a stream of requests for 1-byte files,
> each file will be sent back in a separate small packet.  But that's
> still an improvement over the non-keepalive case (and equivalent to
> the packetization that we get from 1.3).

I wonder if we could also tie the uncork on Linux to the non-keepalive case
without making it too messy?  In other words, if we are doing a whole bunch of
keepalive requests, only uncork after the last one to minimize the number of
packets.  Maybe the uncork could be deferred until just before the socket
shutdown() or close().  

Greg