W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2011

#283: Set expectations around buffering

From: Mark Nottingham <mnot@mnot.net>
Date: Wed, 22 Jun 2011 11:35:45 +1000
Message-Id: <74B4587B-9B2C-4981-AE59-EE537F622E3D@mnot.net>
To: httpbis Group <ietf-http-wg@w3.org>

Proposal for a new section after 2.1 Client/Server? Messaging

2.2 Message Orientation and Buffering

Fundamentally, HTTP is a message-based protocol. Although message bodies can be chunked [ref to chunked encoding] and implementations often make parts of a message available progressively, this is not required, and some widely-used implementations only make a message available when it is complete. Furthermore, while most proxies will progressively stream messages, some amount of buffering will take place, and some proxies might buffer messages to perform transformations, check content or provide other services.

Therefore, extensions to and uses of HTTP cannot rely on the availability of a partial message, or assume that messages will not be buffered. There are strategies that can be used to test for buffering in a given connection, but it should be understood that behaviours can differ across connections, and between requests and responses.

... with a reference to the new section somewhere in 7.2. Message Transmission Requirements.

Mark Nottingham   http://www.mnot.net/
Received on Wednesday, 22 June 2011 01:36:23 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:13:52 UTC