- From: Fernando via GitHub <sysbot+gh@w3.org>
- Date: Fri, 23 Jun 2023 23:25:35 +0000
- To: public-webrtc-logs@w3.org
Hey, just sharing here our experience. I hit this issue while trying to integrate webRTC to our app. We were already using Firestore so it was handy to use it too for the signaling. Specifically, clients write messages (documents) to specific subcollections owned by individual users and it works fine most of the time. But Firestore doesn't guarantee order of insertion for the listeners, I could reproduce out of order messages by causing problems to the network. Having WebRTC dealing with out of order messages would have made the integration path easier and safer. We are going to try @Sean-Der approach and track errors and out of order messages. If we see problems, we might need to make more drastic changes to our architecture... But if WebRTC by itself would handle that and avoid us some work, that would be amazing. Is there any problems in queuing ICE candidates by ufrag and using them after processing the corresponding SDP? Does the order between candidates matter? -- GitHub Notification of comment by fbarbat Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2519#issuecomment-1605119392 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 23 June 2023 23:25:41 UTC