| Revision as of 12:40, 28 November 2004 edit192.108.115.2 (talk) Layout← Previous edit | Revision as of 12:42, 28 November 2004 edit undo192.108.115.2 (talk) StyleNext edit → | ||
| Line 5: | Line 5: | ||
| See also: | See also: | ||
| *A faq on pipelining, courtesy of mozilla.org: http://www.mozilla.org/projects/netlib/http/pipelining-faq.html | *A faq on pipelining, courtesy of mozilla.org: http://www.mozilla.org/projects/netlib/http/pipelining-faq.html | ||
| * |
*A w3c page measuring the benefits of pipelining, along with modern design technologies (CSS and png): http://www.w3.org/TR/NOTE-pipelining | ||
Revision as of 12:42, 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:
- A faq on pipelining, courtesy of mozilla.org: http://www.mozilla.org/projects/netlib/http/pipelining-faq.html
- A w3c page measuring the benefits of pipelining, along with modern design technologies (CSS and png): http://www.w3.org/TR/NOTE-pipelining