W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > April 2020

Re: [webrtc-pc] addIceCandidate may not need to throw an error when no remoteDescription (#2519)

From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
Date: Thu, 30 Apr 2020 20:15:30 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-622085409-1588277729-sysbot+gh@w3.org>
@Sean-Der Please show me a simple example demonstrating the problem.

> > most queuing I've seen only works on initial negotiation
> This is all I am looking for! I think after the initial negotiation all the logic stays the same.

The same methods and logic are used on renegotiation, so we have to think about that as well. E.g.
* App adding new tracks for a participant or screen-sharing sends additional ICE candidates
* App defers adding tracks until after initial negotiation
* App restarts ICE e.g. after connection failure
* App stops a BUNDLE transceiver

GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2519#issuecomment-622085409 using your GitHub account
Received on Thursday, 30 April 2020 20:15:32 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:50 UTC