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

[Bug 14704] New: appcache: allow a manifest to be identified by something other than its URL

From: <bugzilla@jessica.w3.org>
Date: Sat, 05 Nov 2011 21:38:31 +0000
To: public-html@w3.org
Message-ID: <bug-14704-2495@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14704

           Summary: appcache: allow a manifest to be identified by
                    something other than its URL
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: annevk@opera.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org, adrianba@microsoft.com,
                    tobie.langel@gmail.com, blizzard@0xdeadbeef.com


Large server setups use URL fingerprinting for caching. Basically you have the
same resource distributed over many servers and the only way to update it is by
changing its URL. See also:
http://code.google.com/speed/page-speed/docs/caching.html

Cache manifests are incompatible with this model by having a URL identify the
cache. To address this case we should have a separate identifier, probably tied
to the origin of the manifest, that identifies the manifest. In the absence of
such an identifier the URL would still identify the manifest.

(As an aside, we cannot identify the manifest by its master entries, because
they can change over time.)

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Saturday, 5 November 2011 21:38:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:41 GMT