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

[presentation-api] Add a PresentationConnection.disconnected state for accidental disconnections

From: Mark Foltz via GitHub <sysbot+gh@w3.org>
Date: Fri, 06 Nov 2015 01:05:25 +0000
To: public-secondscreen@w3.org
Message-ID: <issues.opened-115412049-1446771924-sysbot+gh@w3.org>
mfoltzgoogle has just created a new issue for 
https://github.com/w3c/presentation-api:

== Add a PresentationConnection.disconnected state for accidental 
disconnections ==
Some interactive applications (e.g., games) may want to pause when the
 controller has accidentally disconnected.  Right now this can only be
 detected indirectly when a call to `connection.send()` fails - the 
connection will transition to `closed` and fire an error event.  To 
detect this quickly, the application would likely need some kind of 
heartbeat mechanism - depending on the channel implementation.

This issue tracks whether we want to add back a `disconnected` state 
so the application can more directly be notified when this happens.  
This implies the implementation would need to come up with its own 
heartbeat mechanism under the covers.

@sicking, feel free to add more context.


See https://github.com/w3c/presentation-api/issues/217
Received on Friday, 6 November 2015 01:05:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:18:59 UTC