[Bug 14702] appcache: always up-to-date applications

https://www.w3.org/Bugs/Public/show_bug.cgi?id=14702

--- Comment #26 from michaeln@google.com 2011-12-14 00:04:07 UTC ---
> > Is that satisfactory?

Lets iterate a bit more prior to putting something in the draft. Once in
draft'eese, the first task for readers is to reverse engineer the
code-written-in-english to understand what it actually says. Let's clarify it
in plain language first, then translate to spec-eese.

> - if the file comes back 200, then act as if you were not associated with an
appcache (same as the first time you fetch a file that later is found to have a
manifest), except use the existing appcache as an HTTP cache. Once the appcache
update is complete, treat the appcache as if it was guaranteed to hold the
latest copies of everything it has, so you never have to hit the network for
cached resources. If the file is found to not have a manifest="", then mark the
entry as foreign.

That behavior sounds somewhat similar to the 'useManifest' or
'dontCacheMasters' behavior that i have in mind, but has the downside of having
only applying to specific urls that are listed in the new manifest section.
Listings like that are tedious and error prone to produce.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 14 December 2011 00:06:11 UTC