- From: Matt Hammond via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 May 2015 17:45:45 +0000
- To: public-secondscreen@w3.org
Some underlying protocols may not support terminating/closing the 2nd screen content. In DIAL, the ability to "stop" an application is optional [1]. Similarly HbbTV (that builds ontop of DIAL) does not mandate this functionality. The behaviour is also not always needed. For example: a user browses a catalogue of video on demand on a mobile device and chooses a show. They "cast" it to the TV to watch it there and will continue to watch it, even if they close the webpage on the mobile device or take some other action within that page that moves them onto looking at other content on the primary screen. I would therefore propose that `session.close()` or `session.terminate()` can fail silently if the underlying protocol does not support this action. Alternatively the requirement to support a close/terminate capability could be indicated when checking availability or trying to start a session. [1] DIAL 1.7.1 spec section 4 or 6.4 at http://www.dial-multiscreen.org/dial-protocol-specification -- GitHub Notif of comment by matt-hammond-bbc See https://github.com/w3c/presentation-api/issues/35#issuecomment-101756660
Received on Wednesday, 13 May 2015 17:45:46 UTC