Re: onicegatheringstatechange VS onicecandidate with candidate==null (just one of them, please)

2014-12-27 22:51 GMT+01:00 Eric Rescorla <ekr@rtfm.com>:
> I'm not convinced this is a good idea.

It is not an idea, it is what it is written in the latest draft:

http://w3c.github.io/webrtc-pc/#widl-RTCPeerConnection-onicegatheringstatechange



> The null candidate lets an implementation
> simply send the candidates to the other side and the null candidate can be
> used to know that no more candidates are coming. That seems simpler than
> having a special app affordance to indicate this.

The latest draft also states:


-----------------------
If the intent of the ICE Agent is to notify the script that:

- The gathering process is done.
Set connection's ice gathering state to completed and let newCandidate be null.
----------------------

So we have two events to say the same. Obviously one of them is redundant.


-- 
Iñaki Baz Castillo
<ibc@aliax.net>

Received on Saturday, 27 December 2014 22:02:17 UTC