- From: Philipel-WebRTC via GitHub <sysbot+gh@w3.org>
- Date: Mon, 03 Jun 2024 11:01:15 +0000
- To: public-webrtc-logs@w3.org
I'm leaning towards only having one `sendRtp` function, but it should only put the packet directly on the wire (UC2). I know this is somewhat counter to the piecemeal approach. > If you're concerned about preventing JS from trying to send both paced and unpaced packets on the same send stream, we'll have the same issue with separate functions. Since BWE and CC is transport wide, we can't have paced and unpaced streams at the same time. Either the app paces *all* streams, or none at all. This is why I think it makes sense for `sendRtp` to have different semantics depending on `RTCConfiguration.customPacer` -- GitHub Notification of comment by Philipel-WebRTC Please view or discuss this issue at https://github.com/w3c/webrtc-rtptransport/issues/32#issuecomment-2144906217 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 3 June 2024 11:01:15 UTC