- From: Matt Hammond via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 May 2015 19:28:09 +0000
- To: public-secondscreen@w3.org
Some questions that I think arise from this: Can there be a mechanism to pass additional parameters to the availability checking and/or session starting process? ([issue-81](https://github.com/w3c/presentation-api/issues/81#issuecomment-101065154) and [issue-9](https://github.com/w3c/presentation-api/issues/9)) Does closure/termination just mean disconnection of the communication link with the 2nd screen presentation? or does it mean the 2nd screen presentation must be terminated? ([issue-35](https://github.com/w3c/presentation-api/issues/35)) Could a resumed session be, temporarily in a disconnected state? Does it matter if the rejoining process cannot guarantee that you are communicating with the same instance of the same URL being presented on the HbbTV device? Security: given that the HbbTV device cannot be trusted by the UA and the message communication mechanism is non-TLS Websockets, what should happen for secure origins? ([issue-45](https://github.com/w3c/presentation-api/issues/45), [issue-63](https://github.com/w3c/presentation-api/issues/63#issuecomment-101045487)) -- GitHub Notif of comment by matt-hammond-bbc See https://github.com/w3c/presentation-api/issues/67#issuecomment-101784461
Received on Wednesday, 13 May 2015 19:28:11 UTC