- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Fri, 19 Mar 2021 11:37:00 +0000
- To: public-webrtc@w3.org
alvestrand has just created a new issue for https://github.com/w3c/webrtc-encoded-transform: == Generalize ScriptTransform constructor == The RTCRtpScriptTransform constructor takes a Worker argument, limiting the usage of this form of the transform to Workers. The older createEncodedStreams() function was agnostic as to where the processing was going to take place; a number of existing demos and apps have been written that do processing on the main thread; some have even prototyped both worker-based and main-thread-based processing and deliberately chosen main-thread-based processing. The normal use case should be worker - but other use cases should be possible. Proposal: Change the argument type of the constructor from Worker to (Worker or MessagePort). Dispatch the event (which could then be a message) on either the worker's implicit port or the explicit MessagePort. This allows all the use cases that the older API allowed, but ensures that the simplest code will be the one invoking a Worker. Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/89 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 19 March 2021 11:37:01 UTC