[squid-users] Re: Persistent Server connections, pipelining and matchingresponses

The answer you are looking for is true for almost any / all Server Daemons that are not multi-threaded. Imagine every "Request" and "Response" as a separate task that is done independently of all the others, and bound together via some type of identification tags or pointers in memory that are then compared to match up to each other. If Squid were to send a single GET across a connection, it will wait for the data to be received in that connection before reusing it, if at all. Otherwise, just like any other daemon, the connection is dropped, and a new connection is opened for more data. It's all done on a "case-by-case" basis.

---------------------------------------------
Chad E. Naugle
Tech Support II, x. 7981
Travel Impressions, Ltd.
 

>>> cachenewbie <email2srini_at_yahoo.com> 9/15/2010 5:00 PM >>>

Hi Chad - Thanks. How does it work for a single client that has pipelining
implemented. If two GET requests are sent to the server and if
hypothetically ( a poorly implemented) server responds only to the second
GET, how does squid (and the client) map the response to the second request
? If squid happens to cache that response, any subsequent client requesting
that resource could get the wrong page served. This is possible right ?
Essentially, squid continues to depend on the "sequence" of the responses
from the origin server and has no way of matching responses to particular
request (even from the same client).

Thanks,

-- 
View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Persistent-Server-connections-pipelining-and-matching-responses-tp2540989p2541220.html 
Sent from the Squid - Users mailing list archive at Nabble.com.
Travel Impressions made the following annotations
-------------------------------------------------------------
"This message and any attachments are solely for the intended recipient and may contain confidential or privileged information.  If you are not the intended recipient, any disclosure, copying, use, or distribution of the information included in this message and any attachments is prohibited.  If you have received this communication in error, please notify us by reply e-mail and immediately and permanently delete this message and any attachments.
Thank you."