> There are very strong reasons at the TCP/IP level why this
> recommendation exists. The goal of connection management in HTTP/1.1 is
> to transform web browsing to a well behaving application according to
I've always appreciated this reason, but end users tend to work on
subjective behaviour (and commercial product developers tend to react
by creating products which optimise for the individual user whilst
making the system as a whole work less efficiently. (I call this
selfish optimisation.))
It seems to me that serialisation of images by HTTP 1.1 compliant
browsers may well be counter productive and lead to either users
bypassing caches or browser sellers abandoning the 2 connection limit.
What we tend to see on the list is the user pressure as applied to
the cache operators, as the first step before the user bypasses the
cache.
--
David Woolley - Office: David Woolley <[EMAIL PROTECTED]>
BTS Home: <[EMAIL PROTECTED]>
Wallington TQ 2887 6421
England 51 21' 44" N, 00 09' 01" W (WGS 84)
Any views expressed in this message are those of the individual sender,
except where the sender specifically states them to be the views of BTS.
