Ignore:
Timestamp:
Jun 29, 2011, 2:14:48 AM (8 years ago)
Author:
julian.reschke@…
Message:

set expectatiions around buffering (see #283)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r1313 r1316  
    620620<x:span anchor="exbody">Hello World!
    621621</x:span></artwork></figure>
     622</section>
     623
     624<section title="Message Orientation and Buffering" anchor="message-orientation-and-buffering">
     625<t>
     626   Fundamentally, HTTP is a message-based protocol. Although message bodies can
     627   be chunked (<xref target="chunked.encoding"/>) and implementations often
     628   make parts of a message available progressively, this is not required, and
     629   some widely-used implementations only make a message available when it is
     630   complete. Furthermore, while most proxies will progressively stream messages,
     631   some amount of buffering will take place, and some proxies might buffer
     632   messages to perform transformations, check content or provide other services.
     633</t>
     634<t>
     635   Therefore, extensions to and uses of HTTP cannot rely on the availability of
     636   a partial message, or assume that messages will not be buffered. There are
     637   strategies that can be used to test for buffering in a given connection, but
     638   it should be understood that behaviors can differ across connections, and
     639   between requests and responses.
     640</t>
    622641</section>
    623642
     
    58965915      "HTTP-Version should be redefined as fixed length pair of DIGIT . DIGIT"
    58975916    </t>
     5917    <t>
     5918      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/283"/>:
     5919      "Set expectations around buffering"
     5920    </t>
    58985921  </list>
    58995922</t>
Note: See TracChangeset for help on using the changeset viewer.