W3C home > Mailing lists > Public > public-secondscreen@w3.org > June 2015

Re: [presentation-api] Allow page to turn itself into a presentation session

From: François Daoust via GitHub <sysbot+gh@w3.org>
Date: Mon, 08 Jun 2015 09:58:21 +0000
To: public-secondscreen@w3.org
Message-ID: <issue_comment.created-109937312-1433757501-sysbot+gh@w3.org>
@avayvod said:

> To join the presentation started from A, B only needs to know the 
URL, not id.

I think I'm starting to get what I misunderstood ;) I had assumed that
 we wanted the following user prompt to be possible on B:

Hello user, this page is willing to present [[url]] on a second 
What do you want to do?
 1. start a new session on C
 2. connect to the session already running on C

... that is, to let the user on B decide whether to start a new 
presentation or to connect to the running session on C. For that to be
 possible, on top of knowing the URL, B would also need to know that C
 is actually running a presentation session for that URL. In the 
generic case, that would mean C advertising the URL on the network.

But that is not what will happen. Instead:
* on B, the user prompt will just contain "connect to C"
* it is up to C to connect the incoming request to the running session
 or to create a new one (or possibly to prompt the user if such an 
interaction is possible)

There is no need for C to advertise anything. Is that correct?

If need arises, we may always add an optional boolean parameter to 
startSession later on that says "start a new session", so that the 
user prompt on B could propose:

 1. connect to C (and start a new session)
 2. connect to C (and join running session if there's one)

> A shared TV could have a browser or an interactive webapp (e.g. 
Spotify) that can be used without presenting (via remote control / 
TV's touch screen). Now I may want to allow my guests to connect to 
the screen to add their music to the queue using Presentation API but 
don't want any info saved - so while the page has connections from 
other clients, it shouldn't be able to save or remember anything. 
Perhaps we should have a method similar to opening a window for the 
page to become a presentation... So the interactive page calls this 
method and its presentation version is loaded in the incognito context
 and is ready to be connected to. We may want the initial page to be 
able to message the presentation one turning it into a special case of
 the Presentation API :)

And so couldn't this be done with `window.open` already (at least from
 a technical perspective, UX might be another issue)? The interactive 
Webapp could open a page that turns itself into a presentation session
 that others connect to.

GitHub Notif of comment by tidoust
Received on Monday, 8 June 2015 09:58:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:18:56 UTC