* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Changeset 1317


Ignore:
Timestamp:
2011-06-29 04:58:06 (3 years ago)
Author:
julian.reschke@gmx.de
Message:

explain that messages need to be considered in isolation (see #288)

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

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

    r1316 r1317  
    935935         not be buffered. There are strategies that can be used to test for buffering in a given connection, but it should be understood 
    936936         that behaviors can differ across connections, and between requests and responses. 
     937      </p> 
     938      <p id="rfc.section.2.2.p.3">Recipients <em class="bcp14">MUST</em> consider every message in a connection in isolation; because HTTP is a stateless protocol, it cannot be assumed that two requests 
     939         on the same connection are from the same client or share any other common attributes. 
    937940      </p> 
    938941      <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;<a id="transport-independence" href="#transport-independence">Connections and Transport Independence</a></h2> 
     
    35933596         </li> 
    35943597         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/283">http://tools.ietf.org/wg/httpbis/trac/ticket/283</a>&gt;: "Set expectations around buffering" 
     3598         </li> 
     3599         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/288">http://tools.ietf.org/wg/httpbis/trac/ticket/288</a>&gt;: "Considering messages in isolation" 
    35953600         </li> 
    35963601      </ul> 
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r1316 r1317  
    638638   it should be understood that behaviors can differ across connections, and 
    639639   between requests and responses.  
     640</t> 
     641<t> 
     642   Recipients &MUST; consider every message in a connection in isolation; 
     643   because HTTP is a stateless protocol, it cannot be assumed that two requests 
     644   on the same connection are from the same client or share any other common 
     645   attributes.  
    640646</t> 
    641647</section> 
     
    59195925      "Set expectations around buffering" 
    59205926    </t> 
     5927    <t> 
     5928      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/288"/>: 
     5929      "Considering messages in isolation" 
     5930    </t> 
    59215931  </list> 
    59225932</t> 
Note: See TracChangeset for help on using the changeset viewer.