Re: [mediacapture-handle] Should the handle be an object? (#68)

So to clarify the illustration further:
- *capturee* gets a broadcasty channel to all current (and for the last message, future) capturers (where the last message is cached and duplicated to new capturers when they start). This message can be any serializable object, and the capturee doesn't learn it's being captured.
- *capturer* gets a single-recipient channel to the capturee, which allows object transfer, of e.g. a `MessagePort` to establish a one-on-one "connection" if it so wishes, revealing to the capturee it is being captured.

-- 
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-handle/issues/68#issuecomment-1285755196 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 15:33:18 UTC