- From: Sean DuBois via GitHub <sysbot+gh@w3.org>
- Date: Mon, 04 May 2020 05:50:20 +0000
- To: public-webrtc-logs@w3.org
> @Sean-Der Please show me a simple example demonstrating the problem. > Something like [this](https://jsfiddle.net/3y8zebL9/)? I took this from a highly voted answer on SO [here](https://stackoverflow.com/a/49055883/5472819). I add the `setTimeOut` just to make it happen everytime. If I am a new developer reading the official [webrtc.org docs on Trickle ICE](https://webrtc.org/getting-started/peer-connections) why would I set onicecandidate after `SetLocalDescription`? > What signaling channel are people bitten by this using? Disregard this, it is really a niche case. If we discuss this it is distracting from the main discussion IMO. Sorry for bringing it up > The same methods and logic are used on renegotiation, so we have to think about that as well. E.g. I don't think this adds any new problems for renegotation? After the first remote-description has been received this remote candidate cache is never used again. -- GitHub Notification of comment by Sean-Der Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2519#issuecomment-623270217 using your GitHub account
Received on Monday, 4 May 2020 05:50:22 UTC