On 8/2/10 5:17 AM, Ian Hickson wrote:
There's a race condition in the media load algorithm. When the resource
selection algorithm begins, it sets a task to complete the rest of the
resource selection algorithm asynchronously.
Not quite. It awaits a stable state and then runs a synchronous section,
which means that it will run the subsequent steps as soon as the current
task has finished, before anything else that is queued.
So the model is that there are asynchronous tasks but there are also
things that run after the "current asynchronous task" finishes?
How are we defining "current asynchronous task" and "finish"? How does
this setup handle cases when the "current asynchronous task" spins the
event loop, if at all?
-Boris
