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

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

From: Shih-Chiang Chien via GitHub <sysbot+gh@w3.org>
Date: Wed, 13 May 2015 04:20:02 +0000
To: public-secondscreen@w3.org
Message-ID: <issue_comment.created-101509232-1431490801-sysbot+gh@w3.org>
I'd like to put my two cents before the F2F meeting.

Currently `PresentationSessionState` only support two states: 
`connected` and `disconnected`, which is not enough for both 
requesting page and presenting page to distinguish between terminating
 the presentation or presentation display being disconnected 
accidentally.

This can be solved by introducing additional state `terminated`. While
 `session.close()` (or rename to `session.terminate()`) being invoked,
 `session.state` will enter `terminated` state. Application can 
reclaim the resources and terminate itself, e.g. closing the window.

-- 
GitHub Notif of comment by schien
See 
https://github.com/w3c/presentation-api/issues/35#issuecomment-101509232
Received on Wednesday, 13 May 2015 04:20:03 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 13 May 2015 04:20:04 UTC