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

Re: [presentation-api] Specify behavior when multiple controlling pages are connected to the session

From: Mark Foltz via GitHub <sysbot+gh@w3.org>
Date: Mon, 15 Jun 2015 18:43:13 +0000
To: public-secondscreen@w3.org
Message-ID: <issue_comment.created-112168261-1434393792-sysbot+gh@w3.org>
@obeletski 

1. Definitely - yes.  The assumption I have made is that when the 
presenting page is loaded the first thing it will want to do is 
establish connectivity to at least one controlling page.

2. I believe this application logic can be handled by either:
  - The presenting page immediately closing any PresentationSessions 
from additional controllers, once the limit is reached;
  - The presenting page signaling to the user agent via a platform 
specific mechanism that no additional controllers should be connected.
I am not sure yet there is a strong use case for adding a property to 
the API to deny further connections when there are alternatives 
available.

3. Again, the presenting page can use `setTimeout` and then deny 
further connections using the mechanisms in #2.

4. I didn't quite follow the scenario you described.  For HbbTV, it 
sounds like the `app-endpoint` could be passed with the presentation 
URL and it could be used to initiate one or more WebSocket connections
 from the presenting page.  Or, the UA could capture the 
`app-endpoint` URL parameter and initiate the connection on the 
presenting page's behalf (wrapping the WebSocket in a 
`PresentationSession`).  

5. It sounds like you're in agreement that the first requirement is 
crucial, and it may be better support the second and third via script 
in the presenting page?


-- 
GitHub Notif of comment by mfoltzgoogle
See 
https://github.com/w3c/presentation-api/issues/19#issuecomment-112168261
Received on Monday, 15 June 2015 18:43:14 UTC

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