- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Tue, 17 May 2022 11:20:57 +0000
- To: public-webrtc-logs@w3.org
> Could you please explain how a single IPC would work? I was meaning a single IPC exchange. > That is not a simple solution. This is a widely used pattern. How is it not a simple solution? Also, please bear in mind that this is an optional optimization. > I think performance is yet another argument in favor of solutions that don't involve communication between render processes. That is a UA implementation choice, this is orthogonal to go with sync or async. Lazy and eager initialisations have both tradeoffs and are both doable. > 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. I disagree with reducing the evaluation to a loss in elegance. About simplicity of implementation, this is of course debatable, I think we should assess it according existing UA patterns. About security, there are AFAIUI no differences. About performances, this seems orthogonal. UA will have to decide between a few additional milliseconds vs. the issues related to a central memory storage, or use hybrid solutions to get the best of both worlds. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/17#issuecomment-1128745904 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 11:20:58 UTC