- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Thu, 19 May 2022 15:16:09 +0000
- To: public-webrtc-logs@w3.org
@yoavweiss, I think there are other approaches that sounds better, for instance: - When creating a CropTarget, register it in renderer process. Send an IPC to the capturer process doing the capture. These are synchronous tasks. No need to wait for capturer process answer. - Capturer process stores a limited set of CropTarget informations based on received IPC, handled using round robin say. - When capturer is asked to crop, capturer looks at its limited set of CropTarget. In 99.99% of the cases, capturer will be able to start right away without waiting for renderer - If no CropTarget is available, send an IPC to renderer which will give back the necessary information to do cropping. This approach removes the capturer process memory capping requirements/privacy issues, removes the need for web pages to have to deal with CropTarget failures, leads to maximum performances in almost all reasonable cases and is reasonably simple. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/17#issuecomment-1131856421 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 19 May 2022 15:16:10 UTC