W3C home > Mailing lists > Public > public-webscreens@w3.org > September 2019

Re: [openscreenprotocol] Multiple controllers of remote playback (#149)

From: Takumi Fujimoto via GitHub <sysbot+gh@w3.org>
Date: Thu, 12 Sep 2019 00:05:12 +0000
To: public-webscreens@w3.org
Message-ID: <issue_comment.created-530611441-1568246710-sysbot+gh@w3.org>
We can allow agents to connect to an existing session without modifying Remote Playback API. It'd allow controlling playback from browser UI, for example. I think we'd want those agents to be able to stop the session, so it'd make sense to just allow full control.

Related: do we want a request message to terminate a session regardless of its type (Presentation, Remote Playback, or streaming)?

If we were to allow creating sessions that can refuse to be controlled by other senders, who should be able to specify this? The controlling page, the controlling agent, or the receiving agent?

---

If we want to let web pages connect to an existing session, we have a few options to do this:
- Allow `RemotePlayback.prompt()` to connect to existing sessions (by having the user select a receiver with an existing session in the browser UI)
- Create a new API that's similar to `PresentationRequest.reconnect()`

Questions:
- What pages do we allow reconnecting? Pages with the same origin as the original sender page? (Pages with the same origin as the media src probably wouldn't work, given the media may be served by a CDN)
- If the local and remote media have different attributes (e.g. src), do we override the local ones with the remote ones?

-- 
GitHub Notification of comment by takumif
Please view or discuss this issue at https://github.com/webscreens/openscreenprotocol/issues/149#issuecomment-530611441 using your GitHub account
Received on Thursday, 12 September 2019 00:05:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:23:19 UTC