- From: Tony Herre via GitHub <sysbot+gh@w3.org>
- Date: Mon, 15 Jul 2024 07:21:38 +0000
- To: public-webrtc-logs@w3.org
`RTCRtpTransportProcessor` in #33 looks good. Would we want to support clearing/assigning a new `hander` mid-stream, like we do in encoded transforms? I don't see a usecase for that level of complexity. Synchronizing that cross-thread is going to be a pain to implement without hidden surprises/dropped packets! For argument's sake, an alternative would be making processor itself transferrable, provided as a direct attribute on `RTCRtpTransport`: ``` interface RTCRtpTransport { Promise addRtpSendStream(RTCRtpSendStreamInit); Promise addRtpReceiveStream(RTCRtpReceiveStreamInit); attribute RTCRtpTransportProcessor processor; } [Exposed=Worker, DedicatedWorker] // Transferable interface RTCRtpTransportProcessor { // as above. } ``` This is the same debate as that taking place in #36 for RtpSendStream/RtpReceiveStream. -- GitHub Notification of comment by tonyherre Please view or discuss this issue at https://github.com/w3c/webrtc-rtptransport/issues/33#issuecomment-2227847343 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 15 July 2024 07:21:38 UTC