- From: Tony Herre via GitHub <sysbot+gh@w3.org>
- Date: Mon, 03 Jun 2024 10:30:34 +0000
- To: public-webrtc-logs@w3.org
I thought they would be merged as a single method, ie `Promise<RtpSendResult> sendRtp(RtpPacketInit packet, optional RtpSendOptions options = {});` with usage: ``` // Send packet with the built in pacer: vanillaSendStream.sendRtp(packet); // Send pacedPacket with specified pacing: pacedSendStream.sendRtp(pacedPacket, {sendTime: 3}); // Actually listen to the send result (probably actually replaced with a batch interface per issue #20) bweSendStream.sendRtp(pacedPacket, {sendTime: congestionController.pace(pacedPacket)}).then((s) => congestionController.sent(s)); ``` 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. -- GitHub Notification of comment by tonyherre Please view or discuss this issue at https://github.com/w3c/webrtc-rtptransport/issues/32#issuecomment-2144849083 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 10:30:35 UTC