[whatwg] Opportunistic caching
ian at hixie.ch
Tue Jun 10 14:46:34 PDT 2008
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 126.96.36.199. Adding a resource whom
> URI matches an opportunistic name space seems to be done only for top
> level documents according to the article 188.8.131.52, 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 184.108.40.206 - "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
> 220.127.116.11.4 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?
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
More information about the whatwg