- From: chcunningham via GitHub <sysbot+gh@w3.org>
- Date: Thu, 11 Nov 2021 00:37:10 +0000
- To: public-webrtc-logs@w3.org
For my part, I remain open to having both APIs. I defer to @drkron to drive investigations and spec updates for preference setting. My only concern with shipping getCapabilities() as-is is the unresolved discussions happening in MC and RTC around decoder capability signalling. While these may appear to be MC issues only, it would be regrettable to have MC and getCapabilities() diverge significantly while co-existing. https://github.com/w3c/media-capabilities/issues/182 (and RTC parallel https://github.com/w3c/webrtc-svc/issues/52) https://github.com/w3c/media-capabilities/issues/183 (and RTC parallel https://github.com/w3c/webrtc-svc/issues/48) -- GitHub Notification of comment by chcunningham Please view or discuss this issue at https://github.com/w3c/webrtc-svc/issues/49#issuecomment-965888057 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 11 November 2021 00:37:13 UTC