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

Re: [webrtc-pc] Candidate from onicecandidate event and addIceCandidate are incompatible

From: Lennart Grahl via GitHub <sysbot+gh@w3.org>
Date: Sat, 18 Mar 2017 12:33:31 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-287542935-1489840410-sysbot+gh@w3.org>
> Also, `{ candidate: '', sdpMid: null, sdpMLineIndex: null, ... }` would be an illegal argument, since either `sdpMid` or `sdpMLineIndex` needs to be specified.

So, `null` does not have the same meaning as the new end-of-candidate event? It's end-of-candidates for a specific media stream? Now I'm starting to understand why you've left `null` in... However, having said that, non-Trickle-ICE implementations can still get the same information by waiting until end-of-candidate has been received for all media streams (although that's a little bit more complicated) - is that correct?

It just seems counter-intuitive to not being able to throw everything that comes out of the `onicecandidate` event into `addIceCandidate` without having to check anything. But I don't feel too strongly about that. Just something users and signalling solutions have to be aware of.

GitHub Notification of comment by lgrahl
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1077#issuecomment-287542935 using your GitHub account
Received on Saturday, 18 March 2017 12:33:37 UTC

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