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

addIceCandidate() mandatory success callback

From: Adam Bergkvist <adam.bergkvist@ericsson.com>
Date: Mon, 10 Mar 2014 17:27:02 +0100
Message-ID: <531DE7D6.7010709@ericsson.com>
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
Hi

What's the intended use for the mandatory success callback for 
addIceCandidate()?

For methods like setRemoteDescription(), the success callback is used as 
a continuation for the application flow; the remote description was 
successfully set and I can go ahead and, for example, create an answer. 
I don't see the same use for the addIceCandidate() success callback. In 
fact, if you would have to wait for that callback before doing anything 
else in your app, it would complicate things a lot. It's pretty 
convenient to be able to treat the candidate exchange as something that 
runs in parallel with your other offer/answer exchanges.

/Adam
Received on Monday, 10 March 2014 16:27:26 UTC

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