| Revision as of 04:15, 22 August 2005 editPeng~enwiki (talk | contribs)320 editsm Reworded and stuff to hopefully make it more encyclopedia-like.← Previous edit | Revision as of 14:51, 9 September 2005 edit undoSuruena (talk | contribs)Extended confirmed users, Pending changes reviewers8,767 editsmNo edit summaryNext 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 latency as separate requests need not be made for each file. | ||
| Since it is possible to fit several HTTP requests in the same ] packet (the average ], or maximum segment size, being 512 ]s), 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 (the average ], or maximum segment size, being 512 ]s), HTTP pipelining allows fewer TCP packets to be sent over the network, reducing network load. | ||
| Line 8: | Line 8: | ||
| * , courtesy of mozilla.org. | * , courtesy of mozilla.org. | ||
| * measuring the benefits of pipelining, along with modern design technologies (] and ]) | * measuring the benefits of pipelining, along with modern design technologies (] and ]) | ||
| ] | ] | ||
Revision as of 14:51, 9 September 2005
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 (the average MSS, or maximum segment size, being 512 bytes), 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)