W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > March 2022

Re: [mediacapture-handle] Don't reinvent postMessage (#11)

From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
Date: Wed, 09 Mar 2022 10:08:53 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-1062757939-1646820531-sysbot+gh@w3.org>
If we were doing rate-limiting, I'd rather do it on the notification end - for instance, change the description of setCaptureHandleConfig's event firing to something like:

Queue a task to execute the following steps:

1. At UA's discretion, insert a short delay to avoid firing too many events
1. set CurrentCaptureHandle to the current value of [[internal slot on capturee indicating last setCaptureHandleConfig]]
2. if it is different from [[internal slot on capturer indicating what was last fired]], fire event

(idea courtesy Jan-Ivar's discussion of reflecting muting on mediacapture-transform)
But again, this is the direction in which we already have a high capacity path (the captured image), so not much of a worry.

GitHub Notification of comment by alvestrand
Please view or discuss this issue at https://github.com/w3c/mediacapture-handle/issues/11#issuecomment-1062757939 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 10:08:55 UTC

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