- From: <bugzilla@jessica.w3.org>
- Date: Wed, 16 Jan 2013 10:34:23 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20677 --- Comment #8 from François REMY <francois.remy.dev@outlook.com> --- (In reply to comment #7) > The appcache system is a way to create a new cache that is bound to the > current browsing context, with a manifest that is atomically downloaded and > its files cached, and that then cuts off the page from the network, using > only the cache. Then, yes, we speak about the 'classical' browser cache (even if a file is in the appcache of the _current_ application, it should return that it's cached too because it won't be loaded over the network). I would also expect the appcache of other apps to be used in a 'conditional' way. If 'http://syn.org/all.json' is appcached by 'syn.org' then the browser should issue an HTTP HEAD If-Modified-Since request to see if it's still up-to-date and call back whether the data is still valid or not. The goal of this API is really to work over NETWORK resources to know if you can use them without triggering their download. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 16 January 2013 10:34:26 UTC