Re: [webrtc-encoded-transform] Add description of an API for controlling SDP codec negotiation (#186)

Codec preferences are decided separately for sender and receiver. The botched `setCodecPreferences` obfuscates that.

> 2. Putting it on the `sender` and `receiver`.

Con: invites people to set codec and transform separately, which has no use case and invites complexity for no gain.

> 3. Adding a `direction` argument for the `transceiver` method.

Con: bad for the same reason we don't put it on pc and pass in transceiver and direction.

> The transceiver needs to know because of `setCodecPreferences` and the sender needs to know because of `setParameters`.

I see no technical _"need"_ here, unless you're suggesting a transceiver cannot see properties on its sender or receiver?

-- 
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/pull/186#issuecomment-1816943432 using your GitHub account


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

Received on Friday, 17 November 2023 19:06:04 UTC