| Revision as of 12:33, 5 May 2006 edit193.252.51.94 (talk)No edit summary← Previous edit | Revision as of 16:12, 5 July 2006 edit undoLee Carre (talk | contribs)Extended confirmed users1,205 editsm →External links: -- changed link text to be more meaningful readability/accessabilityNext edit → | ||
| Line 7: | Line 7: | ||
| == External links == | == External links == | ||
| * , courtesy of mozilla.org. | * , courtesy of mozilla.org. | ||
| * measuring the benefits of pipelining, along with modern design technologies (] and ]) | * A W3C page , along with modern design technologies (] and ]) | ||
Revision as of 16:12, 5 July 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)