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

I tried the [perfect negotiation example](https://w3c.github.io/webrtc-pc/#perfect-negotiation-example) with a simple signaling server (Node.js + Socket.io, WebSocket protocol), and unfortunately, I found that sometimes I receive ICE candidates before the remote description. I had to queue ICE candidates manually, and only for this limitation. I think this problem is more common than we suppose, not surprisingly, as @Sean-Der mentioned, many libraries implement a queue. Please reconsider this limitation, it makes implementing WebRTC difficult and frustrating.

-- 
GitHub Notification of comment by aldovincenti
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2519#issuecomment-730086022 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 19 November 2020 02:32:08 UTC