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

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

From: Jonas Sicking via GitHub <sysbot+gh@w3.org>
Date: Wed, 02 Sep 2015 06:04:01 +0000
To: public-secondscreen@w3.org
Message-ID: <issue_comment.created-136946228-1441173840-sysbot+gh@w3.org>
If I understand correctly, in all of the current proposals, if the 
Chrome application is killed, the PresentationSession would transition
 to a `closed` state and the application running on the TV would be 
notified about this, but nothing else would automatically happen.

Obviously the application could write whatever application logic to 
handle this, such as immediately pausing any running video, or 
immediately closing the application. Or doing either of those things 
after a timeout.

I don't see how adding separate `.close()` and `.terminate()` 
functions would change this?

-- 
GitHub Notif of comment by sicking
See 
https://github.com/w3c/presentation-api/issues/35#issuecomment-136946228
Received on Wednesday, 2 September 2015 06:04:06 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 2 September 2015 06:04:06 UTC