W3C home > Mailing lists > Public > whatwg@whatwg.org > June 2008

[whatwg] Opportunistic caching

From: Honza Bambas <honzab@allpeers.com>
Date: Fri, 13 Jun 2008 23:21:00 +0200
Message-ID: <4852E4BC.8020605@allpeers.com>
Ian Hickson wrote:
> On Tue, 10 Jun 2008, Honza Bambas wrote:
>> Hi, I would like to ask for clarification of opportunistic caching spec 
>> in Offline Web Applications, the article Adding a resource whom 
>> URI matches an opportunistic name space seems to be done only for top 
>> level documents according to the article, cite: "If the resource 
>> was not fetched from..." where the resource refers, as I understand, the 
>> top-level document being navigated.
>> I didn't find any other place where a resource whom URI matched an 
>> opportunistic entry would be added to a cache as opportunistically 
>> cached. I would naturally expect it were part of the networking model, 
>> article - "Changes to the networking model", but I couldn't find 
>> it, at least not explicitly, expressed.
>> Maybe I am missing something in the networking model spec: in article 
>> when URI matches a name space it have to be "fetched 
>> normally". Should implementers replace normal HTTP cache used for 
>> writing by offline cache to store the resource in it? Instead of normal 
>> HTTP cache?
> Resources can only be cached as opportunistically cached entries if a 
> browsing context is navigated, but it doesn't have to be a top-level 
> browsing context. The caching happens in the "Otherwise" clause of step 9 
> of the 4.9.1 Navigating across documents "navigation" algorithm.
> If by "top-level" you don't mean a window/tab, but mean any iframe or 
> frame content document, as opposed to an image, a stylesheet, or some 
> such, then you are correct. The use case was really just replacing pages, 
> e.g. Flickr pages, when the whole site isn't cached. Do you think this 
> should be changed to opportunistically cache anything accessed?
Thanks a lot for clarification.

I was talking with my colleague about it and we both agree it would be 
useful (and more easy to implement) for ANY resource being fetched 
inside of browsing context associated with an application cache to 
opportunistically cache it and not just do it for results of navigation, 
i.e. top-level document, iframe source and frame source. A set o 
pictures/icons/css styles could be easily cached this way w/o explicitly 
listing them in the manifest.

At this point it would be good to say what really is 
intention/motivation of opportunistic caching itself. Maybe I am missing 
the purpose and potentially open a security hole or a kind of attack 
this way.

Honza Bambas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20080613/5bba3198/attachment.htm>
Received on Friday, 13 June 2008 14:21:00 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:03 UTC