- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 May 2021 10:02:30 +0000
- To: public-webrtc-logs@w3.org
The other case I am thinking of is:
sender = pc.addTrack(...)
sender.transform = new RTCRtpScriptTransform(worker, { parameters : await myAsyncOperation() });
This is all fixable by web developers and they should really make sure to do that.
> 1. Do we have legitimate use cases for this functionality?
There could be some usecases though I am not sure how big they are.
For instance dynamically entering a record or screencast mode temporarily where encryption is dropped.
Or setting new SFrameTransform objects instead of changing the keys.
Spec (and prototype) already supports that usecase. It does add limited complexity in practice, thanks to the use of streams API.
> 2\. If no, is there a decent way to say ".transform has to be set before sender/receiver is fully activated, and is read-only thereafter"?
That is the alternative but I did not want to go there since it might not be very clear when it is r/w and when it is readonly.
Say the transceiver is inactive or recvonly. Or the sender active is false.
--
GitHub Notification of comment by youennf
Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/104#issuecomment-839644596 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 12 May 2021 10:02:32 UTC