Changeset 715 for draft-ietf-httpbis/latest/p1-messaging.xml
- Timestamp:
- 21/10/09 15:52:21 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.xml
r713 r715 2260 2260 </t> 2261 2261 <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). 2264 </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. 2269 2283 </t> 2270 2284 </section> … … 4635 4649 </t> 4636 4650 <t> 4651 Remove hard limit of two connections per server. 4652 (<xref target="persistent.practical"/>) 4653 </t> 4654 <t> 4637 4655 Clarify exactly when close connection options must be sent. 4638 4656 (<xref target="header.connection"/>) … … 5249 5267 </t> 5250 5268 <t> 5269 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/131"/>: 5270 "increase connection limit" 5271 </t> 5272 <t> 5251 5273 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/157"/>: 5252 5274 "IP addresses in URLs"
Note: See TracChangeset
for help on using the changeset viewer.