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

Re: [presentation-api] Refine how to do session teardown/disconnect/closing

From: Mark Foltz via GitHub <sysbot+gh@w3.org>
Date: Wed, 02 Sep 2015 16:50:42 +0000
To: public-secondscreen@w3.org
Message-ID: <issue_comment.created-137167297-1441212640-sysbot+gh@w3.org>
@avayvod The expectation is that the controlling user agent will 
provide a way to terminate the presentation (not just a specific 
connection) without requiring a loaded page to have a connected 
session.  It seems like this is a necessary part of any usable 
implementation since there's no guarantee that the user will be able 
to navigate to a page and then get that page to reconnect to the 
presentation, just to be able to call `.terminate()`.  Meanwhile, the 
user agent itself (if it can connect to the display) should be able to
 offer the remote-kill capability (and all protocols I am aware of 
support it). However, it seems like this is difficult to require a 
specific feature with the spec _per se_ however.  

@sicking Yes that's what I'm proposing here.  Another thought is that 
as long as there is a controlling session connected to the page, the 
controller can send a command to the presentation asking it to close 
itself.  Adding `.terminate()` just provides an alternative 
implementation of this function at the presentation network protocol 
level, versus the application protocol level.


-- 
GitHub Notif of comment by mfoltzgoogle
See 
https://github.com/w3c/presentation-api/issues/35#issuecomment-137167297
Received on Wednesday, 2 September 2015 16:50:44 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 2 September 2015 16:50:44 UTC