Re: HTTP 1.1 Pipelining

> I don't think it's uncommon for a web client to open one connection to a
> server to get a document, then open half a dozen more connections to get
> the related images / style sheet, and then keep all of those connections
> open. When the user clicks a link to another document on the same
> server, the connections are all still open, so the second document can
> be retreived even faster.
I think IE only keeps two (or maybe four) connections, in order to be a
'well behaved network citizen' or something. Too many connections from one
client clogs the network or something - but don't quote me on that.