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

Ticket #131: 131.diff

File 131.diff, 2.4 KB (added by julian.reschke@gmx.de, 5 years ago)

Proposed patch for part 1.

  • p1-messaging.xml

     
    22592259   is suspected. 
    22602260</t> 
    22612261<t> 
    2262    Clients that use persistent connections &SHOULD; limit the number of 
    2263    simultaneous connections that they maintain to a given server. A 
    2264    single-user client &SHOULD-NOT; maintain more than 2 connections with 
    2265    any server or proxy. A proxy &SHOULD; use up to 2*N connections to 
    2266    another server or proxy, where N is the number of simultaneously 
    2267    active users. These guidelines are intended to improve HTTP response 
    2268    times and avoid congestion. 
     2262   Clients (including proxies) &SHOULD; limit the number of simultaneous 
     2263   connections that they maintain to a given server (including proxies). 
    22692264</t> 
     2265<t> 
     2266   Previous revisions of HTTP gave a specific number of connections as a 
     2267   ceiling, but this was found to be impractical for many applications. As a 
     2268   result, this specification does not mandate a particular maximum number of 
     2269   connections, but instead encourages clients to be conservative when opening 
     2270   multiple connections. 
     2271</t> 
     2272<t> 
     2273   In particular, while using multiple connections avoids the "head-of-line 
     2274   blocking" problem (whereby a request that takes significant server-side 
     2275   processing and/or has a large payload can block subsequent requests on the 
     2276   same connection), each connection used consumes server resources (sometimes 
     2277   significantly), and furthermore using multiple connections can cause 
     2278   undesirable side effects in congested networks.  
     2279</t> 
     2280<t> 
     2281   Note that servers might reject traffic that they deem abusive, including an 
     2282   excessive number of connections from a client. 
     2283</t> 
    22702284</section> 
    22712285</section> 
    22722286 
     
    46344648  (<xref target="chunked.encoding"/>) 
    46354649</t> 
    46364650<t> 
     4651  Remove hard limit of two connections per server. 
     4652  (<xref target="persistent.practical"/>) 
     4653</t> 
     4654<t> 
    46374655  Clarify exactly when close connection options must be sent. 
    46384656  (<xref target="header.connection"/>) 
    46394657</t> 
     
    52485266      "Repeating single-value headers" 
    52495267    </t> 
    52505268    <t> 
     5269      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/131"/>: 
     5270      "increase connection limit" 
     5271    </t> 
     5272    <t> 
    52515273      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/157"/>: 
    52525274      "IP addresses in URLs" 
    52535275    </t>