cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Donald Ball <>
Subject Re: Content-length
Date Mon, 24 Jan 2000 06:54:39 GMT
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.

- donald

View raw message