- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Fri, 22 Jan 2021 14:52:47 +0000
- To: public-webrtc-logs@w3.org
> I filed [w3c/mediacapture-extensions#16](https://github.com/w3c/mediacapture-extensions/issues/16) so that we do not hijack this thread. Thanks! > > here are plenty of other implementation concerns > > Could you write them down in the above issue? Gladly. > > Transferring 4k frames over IPCs would not be nice. > > I think this is already happening for camera and screen capture in today browsers. Yes, but adding yet more IPCs come at an added cost. > Also, compositing might happen out of process and the process doing the compositing is probably a good place to do tab capture. > > In your specific usecase, the iframes might stay in the same process given they are on the same registrable domain. > Implementations could optimise that code path and skip IPC altogether. I agree that transferability can be simpler in some special cases, like mic/camera and possibly tab-capture. But AFAICT, not so in the general case. Are you suggesting to only allow transfer of MediaStreams between iframes that are same-site? > I think it is important to look at perf and ergonomics. > I am wondering what your assessment of these approaches are in terms of ergonomics for the use case you have in mind and more generally. I completely agree that ergonomics in my particular use case would be superior with transferable streams. My problem is with the performance of the general case, and with the feasibility of implementing transferability only for a set of specific cases. I am also concerned that a solution that is ergonomic for a web-developer when it works (mic/camera, select special cases like tab capture), but sometimes fails for initially-non-obvious reasons (cross-origin MediaStream), might end up less ergonomic. Wdyt? -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/158#issuecomment-765457430 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 22 January 2021 14:52:50 UTC