- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Nov 2023 07:53:03 +0000
- To: public-webrtc-logs@w3.org
Revisiting this issue .... we do have a fundamental disagreement about the need for main-thread support. But it seems to me that if we do it, we could at least agree on a reasonable interface.
Abandoning the messageport idea - how would this look?
interface RTCRtpScriptTransform : EventTarget {
constructor(Worker? worker, optional any options, optional sequence<object> transfer);
attribute EventHandler onrtctransform;
}
With the obvioius semantics that if worker is not specified, the event is fired at the RTCRtpScriptTransform object.
Having this API shape available would (I think) make it possible to support the RTCRtpScriptTransform-based API for the use cases that are supported by the current Chrome interface, and may offer a path to converging the implementations on a single API.
--
GitHub Notification of comment by alvestrand
Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/89#issuecomment-1833265791 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 30 November 2023 07:53:05 UTC