Misplaced Pages

HTTP pipelining: Difference between revisions

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editNext edit →Content deleted Content addedVisualWikitext
Revision as of 00:31, 17 August 2005 edit71.130.254.196 (talk)No edit summary← Previous edit Revision as of 04:15, 22 August 2005 edit undoPeng~enwiki (talk | contribs)320 editsm Reworded and stuff to hopefully make it more encyclopedia-like.Next 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 send multiple answers without closing their socket too. This results in fewer roundtrips and faster load times. This is particularly useful for ] connections 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 cram several HTTP requests in the same ] packet (the average ], or maximum segment size, being 512 bytes), fewer TCP packets are sent over the network, so pipelining benefits network load too. 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.

⚫ 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 these servers are required to allow pipelined requests, they are not required to pipeline responses. Recent versions of the ] support pipelining.


⚫ 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 == == External links ==

Revision as of 04:15, 22 August 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

Category: