Spencer Dawkins wrote:
> I can't tell you this is the RIGHT response to discovering that your server
> doesn't have the same notion of content-length as widely-deployed clients,
> but this was discussed on one of the W3C mailing lists as one of the reasons
> why persistent connections still aren't that common.
Another probably more important reason is the move to more and more
dynamically generated content where the content length isn't known until
after the object has been transmitted (or in some cases buffered, where
a content-length may be calculated on the fly from the buffer).
Other reasons includes a mess of broken implementations in older
browsers. Persistent connections wasn't documented until HTTP/1.1, and
many of the early implemenations (and some of the later as well) didn't
get it right. This mess, rather than bad server implementations may have
forced many server maintainers to disable persistent connections.
-- Henrik Nordstrom
This archive was generated by hypermail 2b29 : Thu Nov 18 2004 - 11:21:26 MST