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: Thu, 10 Sep 2015 16:54:42 +0000
To: public-secondscreen@w3.org
Message-ID: <issue_comment.created-139308539-1441904081-sysbot+gh@w3.org>
@avayvod All good points.  I am in favor of landing a smaller change 
now, and using feedback to add the additional features discussed in 
this thread.

In particular, it seems like the question of the default behavior for 
the presentation when all sessions are disconnected will be difficult 
to answer without additional real world experience.  I can say that 
for Google Cast applications, the default behavior is to leave the 
presentation running; it's suggested that the presentation close 
itself when the last sender disconnects [1], but many implement some 
timeout before doing that.

Here is a simplified version of the proposal in 

enum PresentationSessionState {

partial interface PresentationSession {
    readonly attribute PresentationSessionState state;

    // Both sides transition to "closed."  Presenting context remains
    // running.
    void close(); 

    // All connected sessions transition to "terminated."  Presenting
    // context is closed.
    void terminate();

    // Fired on change to .state
    attribute EventHandler onstatechange;

![presentation session state diagram v2 


I plan to prepare a PR to implement this, 

GitHub Notif of comment by mfoltzgoogle
Received on Thursday, 10 September 2015 16:54:45 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 10 September 2015 16:54:46 UTC