W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > June 2020

Re: [webrtc-pc] RTCRtpSender.getCapabilities() may not return correct information in sync (#2539)

From: henbos via GitHub <sysbot+gh@w3.org>
Date: Mon, 15 Jun 2020 08:17:48 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-643977979-1592209067-sysbot+gh@w3.org>
IMO this API should have been made asynchronous in the first place; codec capabilities means querying HW which means "not synchronous".

While you could still implement this with blocking-invokes I am not in favor of that. Besides, since this reveals information about the system, having it be promise-based would make sense for privacy reasons as well in case a browser wants to implement a prompt (different discussion but worth bringing up if we address this at the same time).

- Make a promise-based version of the API with a different name like queryCapabilities() or something.
- Deprecate the synchronous version of the API.

GitHub Notification of comment by henbos
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2539#issuecomment-643977979 using your GitHub account
Received on Monday, 15 June 2020 08:17:50 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:51 UTC