- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Tue, 01 Jun 2021 17:53:04 +0000
- To: public-webrtc-logs@w3.org
> why not directly expose a MessagePort on the capturing context entangled to another MessagePort exposed on the captured context, instead of an ID. 1. Because it does not address all use-cases as well as exposing a capture-handle. (Note use-cases 2, 3 and 4 in the original message.) 2. Because it's an effort of greater complexity, larger scope, and much more significant security and privacy ramifications. 3. Because it's good to have that as a later extension. You have been advocating small initial scope, after all. I think it would be good, in the future, if our discussions of possible approaches could follow the standard progression of paring down possible solutions. Late proposals for radical deviations from the agreed-upon course are not conducive to reasonably-paced progress. We've been discussing exposure of origin-and-handle for two months now. What's changed? -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/166#issuecomment-852329145 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 1 June 2021 17:53:21 UTC