Re: Multiple request blocking

Adrian Chadd wrote:
>
> On Sat, Jun 30, 2001, Henrik Nordstrom wrote:
> > Seems to be a problem with refreshes when the object is already cached
> > but expired.
> >
> > Not sure what to do about it. Not sure what to do about it, or if it is
> > of general interest to Squid in normal use outside this specific
> > benchmark.
> >
> >
> > Fellow Squid developers: What is your opinion on how/if/when we should
> > chain concurrent requests for the same object before even the status is
> > known?
>
> Why can't we just return an error in the same order as it'd appear
> if the requests weren't pipelined?

Eum.. The question is not at all about pipelining.

It is about the ability for new clients to join a already running server
request for the same object.

Three options exists

a) From start (wanted by Eric, as it takes time before the reply headers
are received as required by 'b')
b) Allowed once it is known that the object should be cachable (current
model)
c) Never

--
Henrik