- From: Elad Alon via GitHub <noreply@w3.org>
- Date: Tue, 03 Jun 2025 21:23:46 +0000
- To: public-webrtc-logs@w3.org
Note that the requirements might not be as tight as they initially appear. The promise should be resolved after it is guaranteed that subsequent frames will not be associated with the old configuration. But there might be arbitrarily many "new" frames issued before the promise resolves. That is, resolving the promise indicates to the app "if you really needed to wait until things were safe, now is safe; but it might have been safe for a few frames." With that in mind, a simple message posted between processes/threads should suffice, I think...? -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/1017#issuecomment-2937242053 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 3 June 2025 21:23:47 UTC