- From: Tony Herre via GitHub <sysbot+gh@w3.org>
- Date: Fri, 16 Aug 2024 08:01:50 +0000
- To: public-webrtc-logs@w3.org
Btw, I've tried out the event-based transfer (using a `createProcessor()` method) in Chromium ([crrev.com/c/5759780](crrev.com/c/5759780)) and an extension to [my sample page](https://tonyherre.github.io/rtptransport-samples/basic_bwe) ([code](https://github.com/tonyherre/rtptransport-samples/commit/2bd545f4089ce74e6cad4fd50902763619d2e27f)). Seems to work quite nicely. I still mildly prefer Transferability but would be fine with this. Discovered that a big benefit of using a `createProcessor()` method on RTCRtpTransport rather than a separate `RTCRtpTransportHandler` constructor is that the processor is ready to be used for the Transport as soon as the `RTCRtpTransportProcessorEvent` is fired in the worker. Otherwise, the worker JS needs to wait some undefined amount of time for the assignment to happen on the main thread and everything to be asynchronously set up by the browser before it can start using the Processor. -- GitHub Notification of comment by tonyherre Please view or discuss this issue at https://github.com/w3c/webrtc-rtptransport/issues/33#issuecomment-2293025853 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 16 August 2024 08:01:50 UTC