W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > November 2011

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

From: <bugzilla@jessica.w3.org>
Date: Fri, 11 Nov 2011 00:29:46 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1ROf06-0001JU-7e@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14702

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ian@hixie.ch
           Severity|normal                      |enhancement

--- Comment #6 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-11-11 00:29:45 UTC ---
So this is basically requesting an entry similar to FALLBACK except that the
resource is only used if it can't be fetched, even if it is already cached the
network is still hit?

I don't understand why this is better than the HTTP cache. If the idea is to
hit the network when you can, but fall back to the cache when the resource is
either not expired or the network is down, then that seems like _exactly_ what
local HTTP caching is for. Appcache is only useful because it lets you get to
the data _before_ you check to see if it's up to date.

-- 
Configure bugmail: http://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 Friday, 11 November 2011 00:29:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 11 November 2011 00:29:54 GMT