- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Wed, 09 Mar 2022 09:16:23 +0000
- To: public-webrtc-logs@w3.org
> A drive-by suggestion: Maybe rate-limiting the calls to `setCaptureHandleConfig()` can reduce the risk of it being used as a bit-by-bit communication channel, while at the same time, continue to enable the use cases of the captured application changing state and wanting to notify the capturer of that. If it helps things along (@jan-ivar?), I am OK with adding rate-limiting initially (as a raised exception), but I'd then like to continue the discussion for removing it. Rationale: Consider a legitimate application that calls `setCaptureHandleConfig()` very rarely. But not necessarily once. It nows needs to worry about those very rare occasions when it makes two calls in overly rapid succession. For example, if a presentation software calls `setCaptureHandleConfig()` whenever changing to another deck, then redirections could happen too rapidly. Such rare bugs are too likely to be missed by developers and end up as bugs. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-handle/issues/11#issuecomment-1062711699 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 9 March 2022 09:16:24 UTC