W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > September to December 1997

Re: Another way to pipeline cache validation....

From: David W. Morris <dwm@xpasc.com>
Date: Thu, 4 Dec 1997 16:13:59 -0800 (PST)
To: Jim Gettys <jg@pa.dec.com>
Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Message-Id: <Pine.GSO.3.96.971204160914.9375B-100000@shell1.aimnet.com>
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/4843

On Thu, 4 Dec 1997, Jim Gettys wrote:

> Andrew's idea is to augment the cache database that a browser keeps on disk 
> of things it caches, with a list of the order in which things are accessed 
> (at that site, maybe with how soon they were accessed).  So when you go 
> see that you need to validate the first class library, it then becomes easy 
> to figure out that there are a bunch of things that the Java application 
> is going to want/need from that web site.  This makes it trivial to do a 
> pipelined cache validation of the set of objects likely to be needed and 
> reduce this to one round trip.  The technique could be used for other forms 
> of cache validation than Java classes as well, but it is obviously a good 
> idea for them. 			

Seems to me that there is an obvious container relationship which could
be exploited by the user agents. As long as the UA is going to change
to improve revalidation performance, the cache management database 
should keep track of the external references from an object.  Simply
following the direct external reference chain should provide a 
directed graph of all objects likely to be required the next time
an object was referenced. A lot better than using relative time
association to guess what else to try.

Dave Morris
Received on Thursday, 4 December 1997 16:23:33 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:21 UTC