- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Thu, 20 Oct 2022 13:17:07 +0000
- To: public-webrtc-logs@w3.org
First, this illustration assumes that the capturee can only be captured by a single capturer. That is false, as I have pointed out in my last message. I have also explained that this should not be abstracted away for the sake of illustration, because it has corollaries. Namely, the only model that **will** work for producing a MessagePort, is one in which the capturee registers to be notified when the capturer tries to establish a MessagePort to it, and this notification has ramifications on issues which you have expressed concern for - self-censorship. Second, this **does not work** for loosely-coupled applications, which would not have advanced agreement on the protocol for the messages sent over the MessagePort. Again - a use-case you have previously said you cared about. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-handle/issues/68#issuecomment-1285524237 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 20 October 2022 13:17:09 UTC