Date: Tue, 28 Jan 1997 15:15:40 +0000 (GMT)
From: David Robinson <drtr@esi.co.uk>
To: new-httpd@hyperreal.com
Subject: Re: [PATCH] must flush for CRLFs after POSTs
In-Reply-To: <ML-2.3.854464133.159.rasmus@inet-dev>
Message-ID: <Pine.BSI.3.91.970128151326.5848B-100000@hume.esi.co.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@hyperreal.com

On Tue, 28 Jan 1997 rasmus@mail1.bellglobal.com wrote:

> > But I'm not sure I like that solution. For one thing, mod_cgi is
> > definitely the wrong place to put it, since POSTs can come
> > anywhere. It would have to be done as part of the http_main loop that
> > controls keepalives. And there's little difference between putting it
> > there and in read_request(), as Dean as suggested.
> 
> Right.  I, for one, would have to clone whatever trick is added to mod_cgi
> for this.  A generic solution in http_main_loop would definitely be preferable.

Sure, I suppose any module can read POST data, therefore the fix for the
extra CRLF data should be in http_main.c or wherever.

I am a bit puzzled as to the original problem. What we are trying to
do here is avoid small write()'s and hence reduce the number of packets
by delaying the delivery of data. Isn't that precisely what the Nagle
algorithm was supposed to achive?

 David.