Re: Squid enhancement thought

On Jun 20, 6:44am, Henrik Nordstrom (possibly) wrote:
> Allen Smith wrote:
> >
> > On Jun 2, 4:24am, Henrik Nordstrom (possibly) wrote:
> > > Dax Kelson wrote:
> > >
> > > > When a user requests a html document, the commercial box scans that html
> > > > document for additional objects (mostly images) and starts retrieving
> > > > those immediately. Shortly after, when the client requests those objects,
> > > > the cache box either has them already, or is already getting them.
> > > >
> > > > Could this be implemented in Squid?
> > >
> > > Could: yes, Is: no, Given priority: very low.
> >
> > A minor version of this that wouldn't be nearly as hard to implement
> > (I've looked at doing it myself, although it's currently pretty far
> > down on my ever-growing list of tasks) would be requesting and caching
> > any cachable referred object (referred via HTTP responses, not HTML
> > coding).
>
> Sorry for the long delay.

That's OK, I haven't had time to work on Squid in quite a while.

> I do not quite follow what your are suggesting here. HTTP referred
> references are not available until the client makes the request

I'm sorry, I may not have been clear enough. What I was referring to
is actually redirection (not referral, technically - my
mis-statement), namely a 3xx status code.

> , and Squid already fetches objects when the client requests them..

Sure, but as long as you know the client is going to be making the
request, and it should be cacheable by the available information, why
not go ahead and request it? It should speed things up a bit, without
increasing bandwidth (except in cases in which the client is
interrupted before making the request for the redirected-to page).

        -Allen

-- 
Allen Smith				easmith@beatrice.rutgers.edu