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

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

From: Eric Rescorla <ekr@rtfm.com>
Date: Sat, 27 Dec 2014 13:51:38 -0800
Message-ID: <CABcZeBO9XnOV69hSEe6P4ft9W+ywx=xhq9j-=JL0j3ELoaEtxQ@mail.gmail.com>
To: Iñaki Baz Castillo <ibc@aliax.net>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
On Sat, Dec 27, 2014 at 1:40 PM, Iñaki Baz Castillo <ibc@aliax.net> wrote:

> Hi, I understand that the way to go is to fire
> onicegatheringstatechange when ICE gathering is done so the user can
> check its status via:
>
>   if (pc.iceGatheringState === 'complete') {  ...  }
>
> Currently that is not implemented in any browser (AFAIK) so the
> old/deprecated onicecandidate with candidate==null is still in use.
>
> Should I understand that once onicegatheringstatechange is
> implemented, browsers won't also emit a onicecandidate with
> candidate==null?


I'm not convinced this is a good idea. 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.

-Ekr
Received on Saturday, 27 December 2014 21:52:47 UTC

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