W3C home > Mailing lists > Public > public-secondscreen@w3.org > April 2017

Re: [presentation-api] Behavior of a receiving user agent in reconnecting

From: Tomoyuki Shimizu via GitHub <sysbot+gh@w3.org>
Date: Tue, 11 Apr 2017 02:14:09 +0000
To: public-secondscreen@w3.org
Message-ID: <issue_comment.created-293129856-1491876848-sysbot+gh@w3.org>
Many thanks, @mfoltzgoogle!

> * Do we think developers would want to keep closed connections around in the list for bookkeeping reasons? For example, to keep track of data for previously connected controllers/players, which could be transferred to a new connection if they rejoin the game.

Yes, but developers can use controller's/player's ID at an application layer to recognize reconnection from the same controller, for example.

> * Do we need to add a `connectionremoved` event to PresentationConnectionList? Presumably the receiving page will have already added a state change handler to

No. A `close` event fired at a PresentationConnection seems to be sufficient.

Okay, I understand that the first option has benefit in terms of implementation and protocol design. Now, my concern is simply that closed presentation connections which are no longer useful for the receiving page still remain in a PresentationConnectionList.

GitHub Notification of comment by tomoyukilabs
Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/419#issuecomment-293129856 using your GitHub account
Received on Tuesday, 11 April 2017 02:14:16 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 11 April 2017 02:14:16 UTC