W3C home > Mailing lists > Public > public-webrtc@w3.org > May 2013

Is onsignalingstatechange synchronous?

From: Jan-Ivar Bruaroey <jib@mozilla.com>
Date: Sat, 11 May 2013 10:35:57 -0400
Message-ID: <518E574D.80209@mozilla.com>
To: public-webrtc@w3.org
Hi everyone!

I'm trying to recall if the point of the Boston interim rename of the 
signalingState states ("have-local-offer" etc.) was about simplifying 
the async question and merely fire onsignalingstatechange synchronously 
on function entry of functions like SetLocalDescription? I seem to read 
that into the language of the spec now as well, but it is not clear 
about it:

explains "have-local-offer" this way:

   "A local description, of type "offer", has been supplied."

What is the definition of "has been supplied" here?


   "This event handler, of event handler event type 
signalingstatechange, MUST be supported by all objects implementing the 
RTCPeerConnection interface. It is called any time the readyState 
changes, i.e., from a call to setLocalDescription, a call to 
setRemoteDescription, or code. It does not fire for the initial state 
change into new."

When does a state "change, from a call to to setLocalDescription" et al. ?

If anyone reading this over the weekend can recall and respond, that 
would be extra great as I'm hoping to have this implementation change in 
for Firefox 23's Monday deadline. Thanks! :-)

..: Jan-Ivar :.
Received on Monday, 13 May 2013 08:30:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:17:43 UTC