[html5] r2351 - [gwr] (2) Appcache: Allow expiring non-manifest files.

[whatwg at whatwg.org]

Author: ianh
Date: 2008-10-17 17:03:44 -0700 (Fri, 17 Oct 2008)
New Revision: 2351

Modified:
   index
   source
Log:
[gwr] (2) Appcache: Allow expiring non-manifest files.

Modified: index
===================================================================
--- index	2008-10-17 23:12:21 UTC (rev 2350)
+++ index	2008-10-18 00:03:44 UTC (rev 2351)
@@ -16,7 +16,7 @@
   <div class=head>
    <p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG src=/images/logo></a></p>
    <h1>HTML 5</h1>
-   <h2 class="no-num no-toc" id=draft-recommendation-—-date:-01-jan-1901>Draft Recommendation — 17 October 2008</h2>
+   <h2 class="no-num no-toc" id=draft-recommendation-—-date:-01-jan-1901>Draft Recommendation — 18 October 2008</h2>
    <p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
    <p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
    <dl><dt>Multiple-page version:</dt>
@@ -34532,7 +34532,20 @@
     following steps. These steps may be run in parallel for two or
     more of the URLs at a time.</p>
 
-    <ol><li><p><a href=#fire-a-simple-event>Fire a simple event</a> called <code title=event-progress><a href=#event-progress>progress</a></code> at the
+    <ol><li>
+
+      <p>If the resource URL being processed was flagged as neither an
+      "explicit entry" nor or a "fallback entry", then the user agent
+      may skip this URL.</p>
+
+      <p class=note>This is intended to allow user agents to expire
+      resources (other than those in the manifest itself) from the
+      cache. Generally, implementors are urged to use an approach that
+      expires lesser-used resources first.</p>
+
+     </li>
+
+     <li><p><a href=#fire-a-simple-event>Fire a simple event</a> called <code title=event-progress><a href=#event-progress>progress</a></code> at the
      <code><a href=#applicationcache>ApplicationCache</a></code> singleton of each <a href=#browsing-context>browsing
      context</a> whose <a href=#active-document>active document</a> is associated
      with a cache in <var title="">cache group</var>. The default

Modified: source
===================================================================
--- source	2008-10-17 23:12:21 UTC (rev 2350)
+++ source	2008-10-18 00:03:44 UTC (rev 2351)
@@ -39220,6 +39220,19 @@
 
     <ol>
 
+     <li>
+
+      <p>If the resource URL being processed was flagged as neither an
+      "explicit entry" nor or a "fallback entry", then the user agent
+      may skip this URL.</p>
+
+      <p class="note">This is intended to allow user agents to expire
+      resources (other than those in the manifest itself) from the
+      cache. Generally, implementors are urged to use an approach that
+      expires lesser-used resources first.</p>
+
+     </li>
+
      <li><p><span>Fire a simple event</span> called <code
      title="event-progress">progress</code> at the
      <code>ApplicationCache</code> singleton of each <span>browsing