- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Tue, 21 Nov 2023 13:46:21 +0000
- To: public-webrtc-logs@w3.org
Thanks for explaining the details. > Separation of concerns dictates that we keep parameters that are chiefly concerned with the SDP on the transceiver level. That's why "setCodecPreferences" is on transceiver level. I disagree there's any need to separate transceiver from sender/receiver to somehow orient the API towards SDP needs. These are 1-1 objects, so we should organize things logically based on function, not SDP. "Early 1.0" versions of the spec (and indeed early implementations of the API for many years) worked fine without transceivers. As I recall, we introduced transceivers chiefly two reasons: 1) direction changes, and 2) stop. setCodecPreferences may also have been a reason, but the reason it is at the transceiver level probably has more to do with the need to put send and receive codecs into a singular order. It was probably just simpler to put this on the transceiver. The direction attribute remains an unfortunate API wort IMHO. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/pull/186#issuecomment-1820956784 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 21 November 2023 13:46:23 UTC