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 12:42, 28 November 2004 edit192.108.115.2 (talk) Style← Previous edit Revision as of 12:48, 28 November 2004 edit undo192.108.115.2 (talk) linkificationNext edit →
Line 1: Line 1:
HTTP pipelining appeared in HTTP/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. 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.


Less TCP packets are sent over the network, since it is possible to cram several HTTP requests in the same TCP packet (the average MSS -max segment size- being 512 bytes). So pipelining benefits network load too. Less TCP packets are sent over the network, since it is possible to cram several HTTP requests in the same TCP packet (the average MSS -max segment size- being 512 bytes). So pipelining benefits network load too.

Revision as of 12:48, 28 November 2004

HTTP pipelining appeared in HTTP/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.

Less TCP packets are sent over the network, since it is possible to cram several HTTP requests in the same TCP packet (the average MSS -max segment size- being 512 bytes). So pipelining benefits network load too.

See also: