| Revision as of 13:26, 28 November 2004 editThe Anome (talk | contribs)Edit filter managers, Administrators253,503 edits ]← Previous edit | Revision as of 12:52, 1 January 2005 edit undoSietse Snel (talk | contribs)Extended confirmed users9,930 editsm dabNext 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. | '''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. | ||
| 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 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. | ||
| {{stub}} | {{stub}} | ||
Revision as of 12:52, 1 January 2005
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.
Since it is possible to cram several HTTP requests in the same TCP packet (the average MSS, or maximum segment size, being 512 bytes), fewer TCP packets are sent over the network, so pipelining benefits network load too.
This article is a stub. You can help Misplaced Pages by expanding it. |
External links
- 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