> > quite that simple - it might allow a few at once.) Browsers may also
> > serialsize requests to Lynx.
^^^^ meant squid.
>
> Squid uses as many connections to the origin server as the browser has
> active connections to Squid, a little more on pipelined requests (up to
This contradicts the recent statement that the use of persistent
connection for client and server sides is independent, although it
did seem to me that it must do multiple connections to the server.
(The HTTP 1.1 guideline is no more than twice the number of users,
presumably meaning browsers, not browser connections, in the ideal
case.)
> twice as many). There is no serialization of requests other than what is
> done by the browser.
As I remember it, the guideline for browsers is to use no more than
two connections when persistent connections are available (presumably
one for the HTML and one for the images and other objects), but they
are likely to start a connection per image, otherwise. (See section
8.1.4 of the HTTP 1.1 specification.) The result of this will tend
to be that only one image is rendered at a time, which may make the
page subjectively slower.
>
> --
> Henrik Nordstrom
> Spare time Squid hacker
>
>
--
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.
