This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
[[ 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?
"Atomically" is a well-understood term in computer science. For your questions, it's not clear if by "algorithm" you mean the whole algorithm, or just the substep that is run atomically. Can you elaborate?
(In reply to comment #1) > "Atomically" is a well-understood term in computer science. > > For your questions, it's not clear if by "algorithm" you mean the whole > algorithm, or just the substep that is run atomically. Can you elaborate? > In 2.3, list of pending master entries is being modified. Should this be isolated from 7.4? In 2.4, 2.5, and 2.6, the status of a cache group is being inspected and in 2.7, the same is being modified. Should these be isolated from 5.6, 7.6, 10, 28, and failure step 6?
> In 2.3, list of pending master entries is being modified. Should this be > isolated from 7.4? > > In 2.4, 2.5, and 2.6, the status of a cache group is being inspected and in > 2.7, the same is being modified. Should these be isolated from 5.6, 7.6, 10, > 28, and failure step 6? Everything in step 2 runs atomically, so it's isolated from everything.