- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Thu, 17 Dec 2020 10:35:49 +0000
- To: public-webrtc-logs@w3.org
AIUI, we want to ensure that calling setCodecPreferences synchronously after getCapabilities should not throw. Similarly, if getCapabilites moves to async, the idea would be that calling setCodecPreferences in the promise resolution microtask would not throw. There should be a similar guarantee if codec capabilities are queried through Media Capabilities. Option 1 and 2 do not solve the usual flow of: 1. creating a peer connection. 2. adding a transceiver 3. calling getCapabilities 3. setting the codec accordingly 4. calling createOffer Option 3 is really an implementation choice. My inclination would be to try something like: 1. Deprecate codecs in synchronous getCapabilities. In the meantime, make it clear to developers of its shortcomings 2. Validate a synchronous getCapabilities is good enough for non codec information 3. Validate/Make sure media capabilities as input to setCodecPreferences is a superior replacement I would go with an async getCapabilities if we cannot validate 2. or 3. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/57#issuecomment-747356681 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 17 December 2020 10:35:51 UTC