- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Tue, 17 May 2022 09:22:12 +0000
- To: public-webrtc-logs@w3.org
> When we discussed this, your objection was that it would be too costly to send IPC messages to each renderer process. I thought we agreed that a single IPC message was ok. Could you please explain how a single IPC would work? > This is a solved problem: IPC messages are usually received in a specific run loop, then processed either in a dedicated run loop or the main loop. That is not a simple solution. I think performance is yet another argument in favor of solutions that don't involve communication between render processes. Engineering deals with trade-offs. The issue of making `produceCropTarget()` async, and the small loss in elegance involved therein, does not seem to me to merit the loss of (i) simplicity of implementation, (ii) strong security guarantees and (iii) performance. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/17#issuecomment-1128631371 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 17 May 2022 09:22:14 UTC