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

[presentation-api] Reconcile sessionavailable vs. sessionconnect for notifying page of session connection

From: Mark Foltz via GitHub <sysbot+gh@w3.org>
Date: Tue, 28 Jul 2015 00:57:52 +0000
To: public-secondscreen@w3.org
Message-ID: <issues.opened-97589682-1438045071-sysbot+gh@w3.org>
mfoltzgoogle has just created a new issue for 
https://github.com/w3c/presentation-api:

== Reconcile sessionavailable vs. sessionconnect for notifying page of
 session connection ==
PR #146 adds a `sessionconnect` event to notify the controlling page 
that a presentation session is now accessible to that page.  However 
we previously introduced `sessionavailable` for this purpose on the 
presenting side.  I propose we use one event for both sides.

`sessionconnect` may not be the best name because on the controlling 
side, the event is fired before the session becomes connected.  
Therefore I propose naming the event `sessionavailable` to denote that
 the session may be disconnected or connected when the event fires.


See https://github.com/w3c/presentation-api/issues/152
Received on Tuesday, 28 July 2015 00:58:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 28 July 2015 00:58:17 UTC