- From: Ralph Giles <giles@thaumas.net>
- Date: Fri, 15 Jul 2011 14:59:44 -0700
- To: public-webrtc@w3.org
- Cc: Cullen Jennings <fluffy@cisco.com>, Ian Hickson <ian@hixie.ch>, Anant Narayanan <anant@mozilla.com>
On 12 July 2011 17:10, Ralph Giles <giles@thaumas.net> wrote: >> In the general case of using the API outside browsers, or even in browsers, how does one solve the race condition that happens after creation of the object and before installing the onIncomgStream callback and the arrival of the first incoming stream? Are they queued ? > > The short answer is, "Yes, they're queued." After further discussion it seems the situation is a bit more complicated. The event loop, as described in Ian's reference[1] does make this safe, by positing multiple task queues which can be prioritized separately. However, we don't currently implement this in gecko. We have a number of hacks to make some sorts of nested event loops work better, but I'm not longer clear that this race would be absolutely prevented until the htm5 event-loop implementation is complete. Can anyone speak on the state of other browsers here? -r [1] http://www.whatwg.org/specs/web-apps/current-work/complete/webappapis.html#event-loop
Received on Friday, 15 July 2011 22:05:59 UTC