- From: Mark Foltz via GitHub <sysbot+gh@w3.org>
- Date: Tue, 17 Mar 2015 00:21:52 +0000
- To: public-secondscreen@w3.org
A related issue is when the page calls `startSession(url, id)` when there is an existing presentation with the same `url` and `id`. The [current algorithm](http://w3c.github.io/presentation-api/#starting-a-presentation-session) indicates that a new presentation session is always started, but the fate of the existing session is not specified. The user agent could: 1. Keep the existing session, which would allow the scenario posted originally in this issue to occur. However, `joinSession` and other algorithms would need to be modified to handle the `(url, id)` ambiguity. 2. Close the existing session only if a different screen was chosen. Otherwise act as if `joinSession` was called and reconnect to the existing presentation. 3. Always close the existing session (even if the same screen was chosen) 2 seems to match the intent of the user in most cases (i.e. redirecting a presentation to a different screen), as opposed to multicasting an identical presentation to multiple screens. -- GitHub Notif of comment by mfoltzgoogle See https://github.com/w3c/presentation-api/issues/39#issuecomment-82003693
Received on Tuesday, 17 March 2015 00:22:01 UTC