W3C home > Mailing lists > Public > public-webrtc@w3.org > April 2014

Re: Please clarify whether onsignalingstatechange fires for the final state change into "closed"

From: Suhas Nandakumar (snandaku) <snandaku@cisco.com>
Date: Sun, 13 Apr 2014 23:18:03 +0000
To: Martin Thomson <martin.thomson@gmail.com>
CC: "Cullen Jennings (fluffy)" <fluffy@cisco.com>, Nils Ohlmeier <nohlmeier@mozilla.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <EEDCCDBA-9F13-4AC7-A911-2007E0F72632@cisco.com>


Sent from my iPhone

> On Apr 13, 2014, at 3:20 PM, "Martin Thomson" <martin.thomson@gmail.com> wrote:
> 
> Async is good.  Note that for cases where close() is called multiple
> times, subsequent calls can either enqueue and no-op later, or check
> if close() is already enqueued and exit out.

+1 

> 
>> On 12 April 2014 11:56, Cullen Jennings (fluffy) <fluffy@cisco.com> wrote:
>> 
>>> On Apr 11, 2014, at 1:44 PM, Nils Ohlmeier <nohlmeier@mozilla.com> wrote:
>>> 
>>> I'm in favor adding clarification that close() is async
>> 
>> +1
> 
Received on Sunday, 13 April 2014 23:18:32 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:38 UTC