- From: Philipel-WebRTC via GitHub <sysbot+gh@w3.org>
- Date: Thu, 13 Jun 2024 14:11:43 +0000
- To: public-webrtc-logs@w3.org
One thing that came up when thinking about how to implement a JS level pacer. The app should have control over the order in which packets are put onto the network, and having `RtpSendStream`s on separate workers would make this difficult. Lets say for example if you want to send a packet from stream A and stream B within a short interval. Now the pacer can post to woker A and worker B so that `RtpSendStream.sendRtp` can be called from the respective worker, but there is no guarantee that worker A will even call `sendRtp` before packet B has been sent. AFAICT the solution to this would be to have all `RtpSendStream`s on the same worker, so the usefulness of making them transferable might be limited. -- GitHub Notification of comment by Philipel-WebRTC Please view or discuss this issue at https://github.com/w3c/webrtc-rtptransport/issues/36#issuecomment-2165793998 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 13 June 2024 14:11:44 UTC