- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 29 Sep 2009 16:47:16 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7767
Summary: Atomic update of application cache is not well-defined
Product: HTML WG
Version: unspecified
Platform: PC
URL: http://dev.w3.org/html5/spec/Overview.html#updating-an-
application-cache
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: HTML5 spec bugs
AssignedTo: dave.null@w3.org
ReportedBy: nikunj.mehta@oracle.com
QAContact: public-html-bugzilla@w3.org
CC: ian@hixie.ch, mike@w3.org, public-html@w3.org
[[
Atomically, so as to avoid race conditions, perform the following substeps:
If the status of the cache group is either checking or downloading, then abort
this instance of the update process, as an update is already in progress for
them.
]]
Atomically is not well defined here.
1. What happens if the state of the cache group changes mid-stream of this
algorithm?
2. If the algorithm is already running when another instance is started, does
the latter instance stay blocked?
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 29 September 2009 16:47:30 UTC