W3C home > Mailing lists > Public > public-html-commits@w3.org > October 2008

html5/spec Overview.html,1.1520,1.1521

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Fri, 17 Oct 2008 22:38:27 +0000
To: public-html-commits@w3.org
Message-Id: <E1Kqxxj-0003CI-A4@lionel-hutz.w3.org>

Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv12276

Modified Files:
	Overview.html 
Log Message:
Appcache: Handle errors for dynamic and master entries differently, since they aren't representative of manifest errors. (whatwg r2348)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1520
retrieving revision 1.1521
diff -u -d -r1.1520 -r1.1521
--- Overview.html	16 Oct 2008 10:53:27 -0000	1.1520
+++ Overview.html	17 Oct 2008 22:38:24 -0000	1.1521
@@ -8,7 +8,7 @@
    <p><a href=http://www.w3.org/><img alt=W3C height=48 src=http://www.w3.org/Icons/w3c_home width=72></a></p>
    <h1>HTML 5</h1>
    <h2 class="no-num no-toc" id=a-vocabulary-and-associated-apis-for-html-and-xhtml>A vocabulary and associated APIs for HTML and XHTML</h2>
-   <h2 class="no-num no-toc" id=editor-s-draft-date-zzz-9-june-2008><!-- "W3C Working Draft" --> Editor's Draft <!--ZZZ-->16 October 2008</h2>
+   <h2 class="no-num no-toc" id=editor-s-draft-date-zzz-9-june-2008><!-- "W3C Working Draft" --> Editor's Draft <!--ZZZ-->17 October 2008</h2>
    <dl><!-- ZZZ: update the month/day
     <dt>This Version:</dt>
     <dd><a href="http://www.w3.org/TR/2008/WD-html5-20080610/">http://www.w3.org/TR/2008/WD-html5-20080610/</a></dd>
@@ -97,7 +97,7 @@
   specification's progress along the W3C Recommendation
   track.
   <!--ZZZ:-->
-  This specification is the 16 October 2008 <!--ZZZ "Working Draft"-->Editor's Draft.
+  This specification is the 17 October 2008 <!--ZZZ "Working Draft"-->Editor's Draft.
   <!--:ZZZ-->
   </p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- relationship to other work (required) --><p>This specification is also being produced by the <a href=http://www.whatwg.org/>WHATWG</a>. The two specifications are
   identical from the table of contents onwards.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- context and rationale (required) --><p>This specification is intended to replace (be a new version of)
@@ -27990,19 +27990,55 @@
 
      <li>
 
-      <p>If the previous steps fails (e.g. the server returns a 4xx or
+      <p>If the previous step fails (e.g. the server returns a 4xx or
       5xx response or equivalent, or there is a DNS error, or the
       connection times out, or the user cancels the download), or if
-      the server returned a redirect, then run the <a href=#cache-failure-steps>cache failure
-      steps</a>.</p>
+      the server returned a redirect, then run the first appropriate
+      step from the following list:</p>
 
-      <p class=note>Redirects are fatal because they are either
-      indicative of a network problem (e.g. a captive portal); or
-      would allow resources to be added to the cache under URLs that
-      differ from any URL that the networking model will allow access
-      to, leaving orphan entries; or would allow resources to be
-      stored under URLs different than their true URLs. All of these
-      situations are bad.</p>
+      <dl class=switch><dt>If the URL being processed was flagged as an "explicit
+       entry" or a "fallback entry"</dt>
+
+       <dd>
+
+        <p>Run the <a href=#cache-failure-steps>cache failure steps</a>.</p>
+
+        <p class=note>Redirects are fatal because they are either
+        indicative of a network problem (e.g. a captive portal); or
+        would allow resources to be added to the cache under URLs that
+        differ from any URL that the networking model will allow
+        access to, leaving orphan entries; or would allow resources to
+        be stored under URLs different than their true URLs. All of
+        these situations are bad.</p>
+
+       </dd>
+
+       <dt>If the error was a 404 or 410 HTTP response or
+       equivalent</dt>
+
+       <dd>
+
+        <p>Skip this resource. It is dropped from the cache.</p>
+
+       </dd>
+
+       <dt>Otherwise</dt>
+
+       <dd>
+
+        <p>Copy the resource and its metadata from <var title="">cache</var>, and ignore the resource obtained from
+        the network.</p>
+
+       </dd>
+
+      </dl><p>User agents may warn the user of these errors as an aid to
+      development.</p>
+
+      <p class=note>These rules make errors for resources listed in
+      the manifest fatal, while making it possible for other resources
+      to be removed from caches when they are removed from the server,
+      without errors, and making non-manifest resources survive
+      server-side errors.
 
      </li>
 
Received on Friday, 17 October 2008 22:38:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 17 October 2008 22:38:42 GMT