This is an old revision of this page, as edited by 192.108.115.2 (talk) at 12:40, 28 November 2004 (First version, uses http://www.mozilla.org/projects/netlib/http/pipelining-faq.html). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
Revision as of 12:40, 28 November 2004 by 192.108.115.2 (talk) (First version, uses http://www.mozilla.org/projects/netlib/http/pipelining-faq.html)(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)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: A faq on pipelining, courtesy of mozilla.org: http://www.mozilla.org/projects/netlib/http/pipelining-faq.html This w3c page measures the benefits of pipelining, along with modern design technologies (CSS and png): http://www.w3.org/TR/NOTE-pipelining