Re: [webrtc-insertable-streams] Should we rename SFrameTransform and RTCRtpScriptTransform (#65)

Firstly, the streams spec is [particular](https://github.com/w3c/webtransport/issues/210#issuecomment-785175824) about what can be called "streams", so we should use "stream" when it fits.

Secondly, [transform streams](https://streams.spec.whatwg.org/#transform-stream) in the platform seem come in pairs:
```webidl
TextEncoderStream includes GenericTransformStream;
TextDecoderStream includes GenericTransformStream;

CompressionStream includes GenericTransformStream;
DecompressionStream includes GenericTransformStream;
```
To follow that would mean changing [from](https://w3c.github.io/webrtc-insertable-streams/#sframe):
```webidl
SFrameTransform includes GenericTransformStream;
```
...to
```webidl
SFrameEncrypterStream includes GenericTransformStream;
SFrameDecrypterStream includes GenericTransformStream;
```

This seems more ergonomic in JS. E.g. instead of 
```js
transceiver.sender.transform = new SFrameTransform();
transceiver.receiver.transform = new SFrameTransform({role: "decrypt");
```
...we'd avoid the boolean arg and just have:
```js
transceiver.sender.transform = new SFrameEncrypterStream();
transceiver.receiver.transform = new SFrameDecrypterStream();
```

-- 
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/webrtc-insertable-streams/issues/65#issuecomment-792365306 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Sunday, 7 March 2021 22:29:17 UTC