[html5] r5286 - [giow] (1) Handle the race condition of a manifest becoming 404 while a page tha [...]
whatwg at whatwg.org
whatwg at whatwg.org
Thu Aug 12 13:32:39 PDT 2010
Author: ianh
Date: 2010-08-12 13:32:38 -0700 (Thu, 12 Aug 2010)
New Revision: 5286
Modified:
complete.html
index
source
Log:
[giow] (1) Handle the race condition of a manifest becoming 404 while a page that uses it is loading.
Modified: complete.html
===================================================================
--- complete.html 2010-08-12 08:33:33 UTC (rev 5285)
+++ complete.html 2010-08-12 20:32:38 UTC (rev 5286)
@@ -62239,6 +62239,12 @@
identify the <a href=#application-cache-group>application cache group</a> to be
updated.</p>
+ <p>If that <a href=#application-cache-group>application cache group</a> is <a href=#concept-appcache-obsolete title=concept-appcache-obsolete>obsolete</a>, then abort
+ this instance of the <a href=#application-cache-download-process>application cache download
+ process</a>. This can happen if another instance of this
+ algorithm found the manifest to be 404 or 410 while this
+ algorithm was waiting in the first step above.</p>
+
</dd>
</dl></li>
@@ -62942,11 +62948,12 @@
<dt>If <var title="">document</var> was loaded from an
- <a href=#application-cache>application cache</a><!--[redundant], and either there is
- no <var title="">manifest URL</var>, or the URL of the <span
- title="concept-appcache-manifest">manifest</span> of the cache's
- <span>application cache group</span> is the same as <var
- title="">manifest URL</var>--></dt>
+ <a href=#application-cache>application cache</a>, and that <a href=#application-cache>application
+ cache</a> still exists (it is not now <a href=#concept-appcache-obsolete title=concept-appcache-obsolete>obsolete</a>)<!--[redundant],
+ and either there is no <var title="">manifest URL</var>, or the URL
+ of the <span title="concept-appcache-manifest">manifest</span> of
+ the cache's <span>application cache group</span> is the same as
+ <var title="">manifest URL</var>--></dt>
<dd>
Modified: index
===================================================================
--- index 2010-08-12 08:33:33 UTC (rev 5285)
+++ index 2010-08-12 20:32:38 UTC (rev 5286)
@@ -62175,6 +62175,12 @@
identify the <a href=#application-cache-group>application cache group</a> to be
updated.</p>
+ <p>If that <a href=#application-cache-group>application cache group</a> is <a href=#concept-appcache-obsolete title=concept-appcache-obsolete>obsolete</a>, then abort
+ this instance of the <a href=#application-cache-download-process>application cache download
+ process</a>. This can happen if another instance of this
+ algorithm found the manifest to be 404 or 410 while this
+ algorithm was waiting in the first step above.</p>
+
</dd>
</dl></li>
@@ -62878,11 +62884,12 @@
<dt>If <var title="">document</var> was loaded from an
- <a href=#application-cache>application cache</a><!--[redundant], and either there is
- no <var title="">manifest URL</var>, or the URL of the <span
- title="concept-appcache-manifest">manifest</span> of the cache's
- <span>application cache group</span> is the same as <var
- title="">manifest URL</var>--></dt>
+ <a href=#application-cache>application cache</a>, and that <a href=#application-cache>application
+ cache</a> still exists (it is not now <a href=#concept-appcache-obsolete title=concept-appcache-obsolete>obsolete</a>)<!--[redundant],
+ and either there is no <var title="">manifest URL</var>, or the URL
+ of the <span title="concept-appcache-manifest">manifest</span> of
+ the cache's <span>application cache group</span> is the same as
+ <var title="">manifest URL</var>--></dt>
<dd>
Modified: source
===================================================================
--- source 2010-08-12 08:33:33 UTC (rev 5285)
+++ source 2010-08-12 20:32:38 UTC (rev 5286)
@@ -70351,6 +70351,13 @@
identify the <span>application cache group</span> to be
updated.</p>
+ <p>If that <span>application cache group</span> is <span
+ title="concept-appcache-obsolete">obsolete</span>, then abort
+ this instance of the <span>application cache download
+ process</span>. This can happen if another instance of this
+ algorithm found the manifest to be 404 or 410 while this
+ algorithm was waiting in the first step above.</p>
+
</dd>
</dl>
@@ -71200,11 +71207,13 @@
<dt>If <var title="">document</var> was loaded from an
- <span>application cache</span><!--[redundant], and either there is
- no <var title="">manifest URL</var>, or the URL of the <span
- title="concept-appcache-manifest">manifest</span> of the cache's
- <span>application cache group</span> is the same as <var
- title="">manifest URL</var>--></dt>
+ <span>application cache</span>, and that <span>application
+ cache</span> still exists (it is not now <span
+ title="concept-appcache-obsolete">obsolete</span>)<!--[redundant],
+ and either there is no <var title="">manifest URL</var>, or the URL
+ of the <span title="concept-appcache-manifest">manifest</span> of
+ the cache's <span>application cache group</span> is the same as
+ <var title="">manifest URL</var>--></dt>
<dd>
More information about the Commit-Watchers
mailing list