Http Pipelining

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.

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

 

<< PreviousWord BrowserNext >>
objectdock
frederick townsend ward
gallus anonymus
christopher bushell
atanarjuat
siemens westinghouse competition
pixie (glamour model)
john fitzhardinge paul butler
umbrella tree
thomas byrne
human rights in turkey
wicken fen nnr
1
william martin cafe
sydney parkinson
john hurst edmondson
david ross lauder
drover
sinitta
probate court
denham golf club railway station
tony mowbray
paratransit
seta river
patrick donohoe
donald mackintosh
majaddid
george julian howell
matthew charles dixon
allan ebenezer ker
dumgoyne
goulburn correctional centre
robert kells
james gandon
henry edward kenny
henry mitchell jones
angus falconer douglas hamilton
george jarratt
virginia overland transportation
alexis charles doxat
budget range
hubert william lewis
percy thompson dean
william dowling