- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Sun, 20 Mar 2022 08:05:19 +0000
- To: public-webrtc-logs@w3.org
Sadly I missed the meeting. Here is what I would do (I actually have a chrome CL for it even), extending RTCRtpSender and Receiver with
```
[CallWith=ScriptState] static void disableGPU();
```
When called *before* creating any peerconnection this disables hardware encoding and decoding respectively.
This is a sledgehammer and a terrible API but making it
* inconvenient to use for the developer (by not integrating nicely)
* inconvenient to use for the user (by requiring a page reload to change the decision)
* clear that it is just an emergency measure
is intentional. This should be covered by appropriate usage metrics, ideally ones allowing to identify large users and then asking them why they feel a need to use it. This API should not be an excuse not to fix bugs ;-)
--
GitHub Notification of comment by fippo
Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/98#issuecomment-1073193432 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 20 March 2022 08:05:20 UTC