- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Fri, 04 Feb 2022 09:16:46 +0000
- To: public-webrtc-logs@w3.org
> IPC with multiple processes is neither simple, nor performant, nor robust. The cost to implementers is greatly reduced when avoiding this. This is a known problem that is solved in modern browsers. A transferred WritableStream should not do multiple IPCes to locate the process of its sink when writing new values. As I said before, I'd like to understand why it would be more difficult with CropTarget than with all these other existing APIs. > What's the downside to any other constituency? It is more costly to both web developers and web engines. It is not consistent with existing Web APIs AFAIK. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/17#issuecomment-1029789637 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 4 February 2022 09:16:47 UTC