- From: Simon Tran via GitHub <sysbot+gh@w3.org>
- Date: Mon, 28 Nov 2022 22:53:16 +0000
- To: public-webrtc-logs@w3.org
> Signaling is implicit & immediate in local-loop demos, and you never "sent" your offer (by not calling answerer.SRD(offer)) before your 1 second delay, while still sending candidates without delay, thus breaking order. E.g. it's as if you'd signaled: What if my signaling channel is slow and/or unreliable? I'm sometimes getting the error that I'm adding ice candidates before `setRemoteDescription` is called, because I'm using a more complex signaling channel that is unreliable (some messages take longer to reach the receiver than others). The only way I can reproduce the problem consistently is by adding a delay before `setRemoteDescription`. This helps mimic real world condition, where ice candidate messages might reach the receiver before the WebRTC offer. -- GitHub Notification of comment by tran-simon Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2519#issuecomment-1329858299 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 28 November 2022 22:53:37 UTC