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

Re: #288: Considering messages in isolation

From: Julian Reschke <julian.reschke@gmx.de>
Date: Wed, 29 Jun 2011 14:01:16 +0200
Message-ID: <4E0B140C.8050704@gmx.de>
To: Mark Nottingham <mnot@mnot.net>
CC: httpbis Group <ietf-http-wg@w3.org>
On 2011-06-28 07:15, Mark Nottingham wrote:
> Milestone set for -15.
> ...

Applied with <http://trac.tools.ietf.org/wg/httpbis/trac/changeset/1317>.

I added it to the new section, which now reads:

2.2.  Message Orientation and Buffering

    Fundamentally, HTTP is a message-based protocol.  Although message
    bodies can be chunked (Section 6.2.1) 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
    behaviors can differ across connections, and between requests and
    responses.

    Recipients MUST consider every message in a connection in isolation;
    because HTTP is a stateless protocol, it cannot be assumed that two
    requests on the same connection are from the same client or share any
    other common attributes.


Best regards, Julian
Received on Wednesday, 29 June 2011 12:01:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:41 GMT