W3C home > Mailing lists > Public > public-html@w3.org > September 2012

[Bug 19063] New: Validated local resource cache

From: <bugzilla@jessica.w3.org>
Date: Tue, 25 Sep 2012 22:02:55 +0000
To: public-html@w3.org
Message-ID: <bug-19063-2495@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19063

           Summary: Validated local resource cache
           Product: HTML WG
           Version: unspecified
          Platform: PC
               URL: http://forums.whatwg.org/viewtopic.php?t=4169
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec
        AssignedTo: dave.null@w3.org
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: ian@hixie.ch, mike@w3.org,
                    public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


This was was cloned from bug 8320 as part of operation LATER convergence.
Originally filed: 2009-11-16 23:27:00 +0000
Original reporter: Ed Palma <edified@gmail.com>

================================================================================
 #0   Ed Palma                                        2009-11-16 23:27:32 +0000 
--------------------------------------------------------------------------------
Local persistent cross site javascript/css (possibly any resource that has a
src attribute) cache browser that validate based on signature? Something like 

<script type="text/javascript" src="/scripts/jquery-min-1.3.3.js?v=132"
local="com.jquery.min.133.js" sig="eaa41fbd734596533e98e557eae39b8b" />

The browser comes with copies of commonly used libraries or has access to a
repository or downloads them from anywhere and validates sigs, using the same
code where sigs match. 
Implementation suggestions and why this is better than a normal cache
here:http://forums.whatwg.org/viewtopic.php?t=4169
================================================================================
 #1   Ian 'Hixie' Hickson                             2010-01-06 08:27:37 +0000 
--------------------------------------------------------------------------------
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: It is too late to be adding features to HTML5, but this might make
sense in a future version. I would recommend approaching browser vendors and
seeing if they are interested in implementing this.
================================================================================

-- 
Configure bugmail: https://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 Tuesday, 25 September 2012 22:02:56 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:34 UTC