- From: Francois Daoust <fd@w3.org>
- Date: Wed, 12 Nov 2014 18:16:15 +0100
- To: "public-secondscreen@w3.org" <public-secondscreen@w3.org>, "public-webscreens@w3.org" <public-webscreens@w3.org>
- CC: "Bassbouss, Louay" <louay.bassbouss@fokus.fraunhofer.de>
Hi all, Louay and I chatted a bit about the following possibility a couple of weeks ago and I don't remember having seen it mentioned on the mailing-list, so here it goes. In essence, once we add the possibility to join an existing session or resume a connection to a running presentation session through a call to "joinSession", it seems natural to add some way for a page to advertise itself as a running presentation session, to avoid having to call "startSession" altogether. A typical use case: "A user starts an application on her Smart TV that displays family pictures and videos in the background. While the application runs, her child opens the application on his tablet, joins the running presentation application on the Smart TV and adds pictures and comments to the slideshow." The Presentation API enables the above scenario... provided the user starts the Smart TV application from another device in the first place. Said differently, the Presentation API enables more complex scenarios (Smart TV + controlling device) to create sessions, which is good, but not the more simple one (Smart TV only), which seems a bit awkward. Or perhaps this could actually already be handled at the UA level: if the UA detects code in a Web app that e.g. listens to presentation session connections, it could perhaps offer an option on the UA's user interface to start the session directly (with a choice that says "and do that automatically next time the app starts"). What do you think? Francois.
Received on Wednesday, 12 November 2014 17:16:27 UTC