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

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

From: Mark Foltz via GitHub <sysbot+gh@w3.org>
Date: Wed, 13 May 2015 17:28:59 +0000
To: public-secondscreen@w3.org
Message-ID: <issue_comment.created-101753191-1431538139-sysbot+gh@w3.org>
Thanks, that seems reasonable.  Other options that I would put forth 
for consideration:

1. Adding a `disconnectReason` property to the `statechange` event 
that lets the page know why the `PresentationSession` was 
disconnected.
2. Adding an error event (and handler) to `PresentationSession.`  If 
the session was terminated accidentally, this would fire.  This is 
similar to `RTCDataChannel` [1], although the semantics of 
`RTCDataChannel.onerror` are not clear from that spec.

[1] http://www.w3.org/TR/webrtc/#rtcdatachannel






-- 
GitHub Notif of comment by mfoltzgoogle
See 
https://github.com/w3c/presentation-api/issues/35#issuecomment-101753191
Received on Wednesday, 13 May 2015 17:29:01 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 13 May 2015 17:29:01 UTC