cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ben Laurie <...@algroup.co.uk>
Subject Re: Content-length
Date Mon, 24 Jan 2000 10:10:36 GMT
Donald Ball wrote:
> 
> On Sun, 23 Jan 2000, Tim Bray wrote:
> 
> > I don't think Cocoon should get in the habit of sending Content-length.
> > If you don't send it, or send a value of 0, browsers sensibly wait until
> > they get EOF.  If you accidentally send the *wrong* number, bad things
> > happen.  The fact that Cocoon currently stores the whole output page
> > as a string is something that you might want to change later; there are
> > a huge number of ouput-caching and lazy-evaluation strategies that
> > mean you probably can't know in advance what the Content-length is.
> >
> > So.... if were still possible to put something in Cocoon that says
> >
> > if (iReallyAbsolutelyForSureKnowWithoutErrorHowManyBytesImGoingToSend)
> > {
> >    sendContentLengthHeader()
> > }
> >
> > and it cost very little to do so, I'd still have to ask, "why bother"?
> 
> HTTP keep-alives. I say we put it in right now for 1.6.1/1.7. When we
> change page generation strategies, we can always take it out again. For
> now, though, it's a no-brainer optimization.

Can't you use the chunked encoding for keep-alives?

Cheers,

Ben.

--
SECURE HOSTING AT THE BUNKER! http://www.thebunker.net/hosting.htm

http://www.apache-ssl.org/ben.html

Y19100 no-prize winner!
http://www.ntk.net/index.cgi?back=2000/now0121.txt

Mime
View raw message