- From: poot <cvsmail@w3.org>
- Date: Sun, 18 Oct 2009 20:00:26 +0900 (JST)
- To: public-html-diffs@w3.org
hixie: Rename the 'application cache update process' to the 'application
cache download process' (whatwg r4169)
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.3315&r2=1.3316&f=h
http://html5.org/tools/web-apps-tracker?from=4168&to=4169
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.3315
retrieving revision 1.3316
diff -u -d -r1.3315 -r1.3316
--- Overview.html 18 Oct 2009 10:54:07 -0000 1.3315
+++ Overview.html 18 Oct 2009 11:00:14 -0000 1.3316
@@ -858,7 +858,7 @@
<li><a href="#a-sample-manifest"><span class="secno">6.9.3.1 </span>A sample manifest</a></li>
<li><a href="#writing-cache-manifests"><span class="secno">6.9.3.2 </span>Writing cache manifests</a></li>
<li><a href="#parsing-cache-manifests"><span class="secno">6.9.3.3 </span>Parsing cache manifests</a></ol></li>
- <li><a href="#updating-an-application-cache"><span class="secno">6.9.4 </span>Updating an application cache</a></li>
+ <li><a href="#downloading-or-updating-an-application-cache"><span class="secno">6.9.4 </span>Downloading or updating an application cache</a></li>
<li><a href="#the-application-cache-selection-algorithm"><span class="secno">6.9.5 </span>The application cache selection algorithm</a></li>
<li><a href="#changesToNetworkingModel"><span class="secno">6.9.6 </span>Changes to the networking model</a></li>
<li><a href="#expiring-application-caches"><span class="secno">6.9.7 </span>Expiring application caches</a></li>
@@ -40872,7 +40872,7 @@
</ol><p>The <dfn id="atom-namespace">Atom namespace</dfn> is: <code>http://www.w3.org/2005/Atom</code></p>
- </div><h2 id="browsers"><span class="secno">6 </span>Web browsers</h2><div class="impl">
+ </div><h2 id="browsers"><span class="secno">6 </span>Web browsers</h2><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><div class="impl">
<p>This section describes features that apply most directly to Web
browsers. Having said that, except where specified otherwise, the
@@ -44692,8 +44692,8 @@
<dd>The resource corresponding to the URL that was given in a
master entry's <code><a href="#the-html-element-0">html</a></code> element's <code title="attr-html-manifest"><a href="#attr-html-manifest">manifest</a></code> attribute. The
- manifest is fetched and processed during the <a href="#application-cache-update-process">application
- cache update process</a>. All the <a href="#concept-appcache-master" title="concept-appcache-master">master entries</a> have
+ manifest is fetched and processed during the <a href="#application-cache-download-process">application
+ cache download process</a>. All the <a href="#concept-appcache-master" title="concept-appcache-master">master entries</a> have
the <a href="#same-origin" title="same origin">same origin</a> as the manifest.
@@ -44756,7 +44756,8 @@
<p>Each <a href="#application-cache-group">application cache group</a> has a <dfn id="concept-appcache-pending-masters" title="concept-appcache-pending-masters">list of pending master
entries</dfn>. Each entry in this list consists of a resource and a
corresponding <code>Document</code> object. It is used during the
- update process to ensure that new master entries are cached.</p>
+ <a href="#application-cache-download-process">application cache download process</a> to ensure that new
+ master entries are cached.</p>
<p>An <a href="#application-cache-group">application cache group</a> can be marked as <dfn id="concept-appcache-obsolete" title="concept-appcache-obsolete">obsolete</dfn>, meaning that it
must be ignored when looking at what <a href="#application-cache-group" title="application cache
@@ -45259,10 +45260,10 @@
</div>
- <h4 id="updating-an-application-cache"><span class="secno">6.9.4 </span>Updating an application cache</h4>
+ <h4 id="downloading-or-updating-an-application-cache"><span class="secno">6.9.4 </span>Downloading or updating an application cache</h4>
<p>When the user agent is required (by other parts of this
- specification) to start the <dfn id="application-cache-update-process">application cache update
+ specification) to start the <dfn id="application-cache-download-process">application cache download
process</dfn> for an <a href="#absolute-url">absolute URL</a> purported to identify
a <a href="#concept-appcache-manifest" title="concept-appcache-manifest">manifest</a>, or for an
<a href="#application-cache-group">application cache group</a>, potentially given a particular
@@ -45273,8 +45274,8 @@
agent <dfn id="shows-caching-progress">shows caching progress</dfn>. Support for this is
optional. Caching progress UI could consist of a progress bar or
message panel in the user agent's interface, or an overlay, or
- something else. Certain events fired during the <a href="#application-cache-update-process">application
- cache update process</a> allow the script to override the display
+ something else. Certain events fired during the <a href="#application-cache-download-process">application
+ cache download process</a> allow the script to override the display
of such an interface. The goal of this is to allow Web applications
to provide more seamless update mechanisms, hiding from the user the
mechanics of the application cache mechanism. User agents may
@@ -45282,17 +45283,17 @@
not show prominent update progress notifications for applications
that cancel the relevant events.</p>
- <p>The <a href="#application-cache-update-process">application cache update process</a> steps are as
+ <p>The <a href="#application-cache-download-process">application cache download process</a> steps are as
follows:
- <ol><li><p>Optionally, wait until the permission to start the cache
- update process has been obtained from the user. This could include
- doing nothing until the user explicitly opts-in to caching the
- site, or could involve prompting the user for permission. The
- algorithm might never get past this point. (This step is
- particularly intended to be used by user agents running on severely
- space-constrained devices or in highly privacy-sensitive
- environments).</li>
+ <ol><li><p>Optionally, wait until the permission to start the
+ <a href="#application-cache-download-process">application cache download process</a> has been obtained
+ from the user. This could include doing nothing until the user
+ explicitly opts-in to caching the site, or could involve prompting
+ the user for permission. The algorithm might never get past this
+ point. (This step is particularly intended to be used by user
+ agents running on severely space-constrained devices or in highly
+ privacy-sensitive environments).</li>
<li>
@@ -45364,8 +45365,9 @@
<li><p>If the <a href="#concept-appcache-status" title="concept-appcache-status">status</a>
of the <var title="">cache group</var> is either <i>checking</i>
- or <i>downloading</i>, then abort this instance of the update
- process, as an update is already in progress for them.</li>
+ or <i>downloading</i>, then abort this instance of the
+ <a href="#application-cache-download-process">application cache download process</a>, as an update is
+ already in progress.</li>
<li><p>Set the <a href="#concept-appcache-status" title="concept-appcache-status">status</a> of <var title="">cache group</var> to <i>checking</i>.</p>
@@ -45458,7 +45460,8 @@
<li><p>Let the <a href="#concept-appcache-status" title="concept-appcache-status">status</a> of <var title="">cache group</var> be <i>idle</i>.</li>
- <li><p>Abort the update process.</li>
+ <li><p>Abort the <a href="#application-cache-download-process">application cache download
+ process</a>.</li>
</ol></li>
@@ -45512,7 +45515,7 @@
(application caches never include fragment identifiers).</p>
<p class="note">HTTP caching rules, such as <code title="">Cache-Control: no-store</code>, are ignored for the
- purposes of the <a href="#application-cache-update-process">application cache update
+ purposes of the <a href="#application-cache-download-process">application cache download
process</a>.</p>
</li>
@@ -45535,7 +45538,8 @@
<li><p>Let the <a href="#concept-appcache-status" title="concept-appcache-status">status</a> of <var title="">cache group</var> be <i>idle</i>.</li>
- <li><p>Abort the update process.</li>
+ <li><p>Abort the <a href="#application-cache-download-process">application cache download
+ process</a>.</li>
</ol></li>
@@ -45787,7 +45791,8 @@
<li><p>If appropriate, remove any user interface indicating
that an update for this cache is in progress.</li>
- <li><p>Abort the update process.</li>
+ <li><p>Abort the <a href="#application-cache-download-process">application cache download
+ process</a>.</li>
</ol></li>
@@ -45918,14 +45923,15 @@
attempt</a>, discard <var title="">cache group</var>
altogether.</p>
- <li><p>Abort the update process.</li>
+ <li><p>Abort the <a href="#application-cache-download-process">application cache download
+ process</a>.</li>
</ol><p>Attempts to <a href="#fetch">fetch</a> resources as part of the
- <a href="#application-cache-update-process">application cache update process</a> may be done with
+ <a href="#application-cache-download-process">application cache download process</a> may be done with
cache-defeating semantics, to avoid problems with stale or
inconsistent intermediary caches.</p>
- <hr><p>User agents may invoke the <a href="#application-cache-update-process">application cache update
+ <hr><p>User agents may invoke the <a href="#application-cache-download-process">application cache download
process</a>, in the background, for any <a href="#application-cache">application
cache</a>, at any time (with no <a href="#cache-host">cache host</a>). This
allows user agents to keep caches primed and to update caches even
@@ -45982,7 +45988,7 @@
<p>Associate <var title="">document</var> with the
<a href="#application-cache">application cache</a> from which it was loaded. Invoke
- the <a href="#application-cache-update-process">application cache update process</a> for that
+ the <a href="#application-cache-download-process">application cache download process</a> for that
<a href="#application-cache">application cache</a>'s <a href="#application-cache-group">application cache
group</a>, with <var title="">document</var> as the <a href="#cache-host">cache
host</a>.</p>
@@ -45999,7 +46005,7 @@
<dd>
- <p>Invoke the <a href="#application-cache-update-process">application cache update process</a> for
+ <p>Invoke the <a href="#application-cache-download-process">application cache download process</a> for
<var title="">manifest URL</var>, with <var title="">document</var> as the <a href="#cache-host">cache host</a> and with
the resource from which <var title="">document</var> was parsed as
the new <a href="#concept-appcache-master" title="concept-appcache-master">master</a>
@@ -46141,7 +46147,7 @@
<dt><var title="">cache</var> . <code title="dom-appcache-update"><a href="#dom-appcache-update">update</a></code>()</dt>
<dd>
- <p>Invokes the application cache update process.</p>
+ <p>Invokes the <a href="#application-cache-download-process">application cache download process</a>.</p>
<p>Throws an <code><a href="#invalid_state_err">INVALID_STATE_ERR</a></code> exception if there is no application cache to update.</p>
@@ -46239,8 +46245,8 @@
</dl><div class="impl">
<hr><p>If the <dfn id="dom-appcache-update" title="dom-appcache-update"><code>update()</code></dfn> method is
- invoked, the user agent must invoke the <a href="#application-cache-update-process">application cache
- update process</a>, in the background, for the <a href="#application-cache">application
+ invoked, the user agent must invoke the <a href="#application-cache-download-process">application cache
+ download process</a>, in the background, for the <a href="#application-cache">application
cache</a> with which the <code><a href="#applicationcache">ApplicationCache</a></code> object's
<a href="#cache-host">cache host</a> is associated, but without giving that
<a href="#cache-host">cache host</a> to the algorithm. If there is no such
Received on Sunday, 18 October 2009 11:00:59 UTC