- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Tue, 26 Apr 2022 16:30:56 +0000
- To: public-webrtc-logs@w3.org
how about this (which may also solve #95):
```
partial interface RTCRtpTransceiver {
undefined setOfferedCodecs(sequence<RTCRtpCodecCapability> codecsToOffer);
undefined setOfferedRtpHeaderExtensions(sequence<RTCRtpHeaderExtensionCapability> headerExtensionsToOffer);
Promise<sequence<RTCRtpCapabilities>> getCapabilities();
};
```
getCapabilities can be async method and we don't need the "kind" even.
RTCCodecCapability would need to be extended by the direction (which was previously implied by whether it came from sender or receiver).
Not sure if we need setOfferedCodecs even, extending setCodecPreferences should be limited to the direction.
Since setOfferedHeaderExtensions hasn't shipped yet I assume we can still make changes to it. While that information is sync it would be nice for symmetry reasons.
Not sure I want the offered + negotiated codecs / extensions, those can be easily extracted from the SDP (as local and remote codecs) so syntactic sugar.
--
GitHub Notification of comment by fippo
Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/100#issuecomment-1110005582 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 26 April 2022 16:30:57 UTC