- From: Jan-Ivar Bruaroey via GitHub <noreply@w3.org>
- Date: Tue, 24 Jun 2025 18:43:42 +0000
- To: public-webrtc-logs@w3.org
Interfaces are also about ergonomics and don't have to be expensive. I'd rather follow the [TextEncoder/DecoderStream](https://encoding.spec.whatwg.org/#interface-textencoderstream) precedent, which suggests `SFrameEncrypterStream` and `SFrameDecrypterStream` (doing away with the `role` switch). > SFrameTransform does more than just apply SFrame encryption ... The generic transform shouldn't have to be bothered by that. And vice versa, the main-thread sender/receiver-assignable (RTC?)SFrameTransform handle-object works without including [GenericTransformStream](https://streams.spec.whatwg.org/#generictransformstream), suggesting a clean break is doable. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/262#issuecomment-3001518102 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 24 June 2025 18:43:43 UTC