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

[webrtc-pc] addIceCandidate end of candidates woes

From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
Date: Sun, 14 May 2017 14:33:33 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-228545622-1494772412-sysbot+gh@w3.org>
fippo has just created a new issue for https://github.com/w3c/webrtc-pc:

== addIceCandidate end of candidates woes ==
there has been much back-and-forth on this... @taylor-b you might know.
How do I make an end-of-candidates indications for all transports that need one?

http://w3c.github.io/webrtc-pc/#dom-rtcpeerconnection-addicecandidate
> If candidate.candidate is an empty string, process candidate as an end-of-candidates indication for the corresponding media description and ICE candidate generation.
This assumes a end of candidates indication for a particular sdpMid/sdpMLineIndex however.

However, http://w3c.github.io/webrtc-pc/#dom-rtcpeerconnectioniceevent still says that the candidate (and therefore the sdpMId and sdpMLineIndex) is null on end-of-candidates and there is only one.

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1213 using your GitHub account
Received on Sunday, 14 May 2017 14:33:40 UTC

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