- From: Kostiainen, Anssi <anssi.kostiainen@intel.com>
- Date: Wed, 30 Aug 2017 13:51:28 +0000
- To: Chris Needham <chris.needham@bbc.co.uk>
- CC: "public-webscreens@w3.org" <public-webscreens@w3.org>, "public-secondscreen@w3.org" <public-secondscreen@w3.org>, "mark a. foltz" <mfoltz@google.com>, Francois Daoust <fd@w3.org>
Hi Chris, All, [Taking this topic off the pull request to list discussion, cross-posting to both WG and CG] In GitHub I asked [1]: [[ Is anyone thinking of using HTTP/2, WebSockets, or a custom protocol anymore? ]] And Chris responded [2]: [[ This is something we should discuss with the Media and Entertainment IG, in relation to TV industry second screen protocols. For example, the companion screen protocol in HbbTV 2.0 uses WebSockets (with SSDP and DIAL) but also UDP for messages involved in synchronising content between screens. ]] Chris - as one of the Media and Entertainment IG chairs, would you like to take this topic back to the IG for discussion? It'd be great if by TPAC joint session we'd be better informed of the TV industry second screen protocol landscape to have a productive discussion. All - as a reminder, the current plan is to have a joint session at TPAC 2017 between the Second Screen WG/CG and the Media and Entertainment IG on Monday afternoon: https://www.w3.org/wiki/Second_Screen/Meetings/Nov_2017_F2F We should start hashing out the Second Screen WG/CG agenda, out of which CG and its Open Screen Protocol discussion is expected to take a significant share this year given the Presentation API and the Remote Playback API are stabilizing. Please feel free to field your suggestions for TPAC agenda items. The wiki is open for your contributions. Or just chime in on this list as usual. Thanks, -Anssi [1] https://github.com/webscreens/openscreenprotocol/pull/44#issuecomment-325917624 [2]: https://github.com/webscreens/openscreenprotocol/pull/44#issuecomment-325983325
Received on Wednesday, 30 August 2017 13:52:00 UTC