| Revision as of 13:48, 11 September 2006 editDerbeth (talk | contribs)Extended confirmed users645 editsm interwiki:pl← Previous edit | Revision as of 16:20, 1 October 2006 edit undoWidefox (talk | contribs)Autopatrolled, Extended confirmed users, Page movers, IP block exemptions, New page reviewers, Pending changes reviewers, Rollbackers107,050 edits linksNext edit → | ||
| Line 1: | Line 1: | ||
| '''HTTP pipelining''' appeared in ]/1.1. It allows clients to send multiple requests at once, without waiting for an answer. Servers can also send multiple answers without closing their socket. This results in fewer roundtrips and faster load times. This is particularly useful for ] and other connections with high latency as separate requests need not be made for each file. | '''HTTP pipelining''' appeared in ]/1.1. It allows clients to send multiple requests at once, without waiting for an answer. Servers can also send multiple answers without closing their socket. This results in fewer ''roundtrips'' and faster load times. This is particularly useful for ] and other connections with high ] as separate requests need not be made for each file. | ||
| Since it is possible to fit several HTTP requests in the same ] packet, HTTP pipelining allows fewer TCP packets to be sent over the network, reducing network load. | Since it is possible to fit several HTTP requests in the same ] packet, HTTP pipelining allows fewer TCP packets to be sent over the network, reducing network load. | ||
| Line 9: | Line 9: | ||
| * A W3C page , along with modern design technologies (] and ]) | * A W3C page , along with modern design technologies (] and ]) | ||
| {{compu-network-stub}} | |||
| ] | ] | ||
Revision as of 16:20, 1 October 2006
HTTP pipelining appeared in HTTP/1.1. It allows clients to send multiple requests at once, without waiting for an answer. Servers can also send multiple answers without closing their socket. This results in fewer roundtrips and faster load times. This is particularly useful for satellite Internet connections and other connections with high latency as separate requests need not be made for each file.
Since it is possible to fit several HTTP requests in the same TCP packet, HTTP pipelining allows fewer TCP packets to be sent over the network, reducing network load.
HTTP pipelining requires both the client and the server to support it. Servers are required to support it in order to be HTTP/1.1 compliant, although they are not required to pipeline responses, just to accept pipelined requests.
External links
- A FAQ on pipelining, courtesy of mozilla.org.
- A W3C page measuring the benefits of pipelining, along with modern design technologies (CSS and PNG)
 | This computer networking article is a stub. You can help Misplaced Pages by expanding it. |