[openscreenprotocol] [Control] Bidirectional control protocol

mfoltzgoogle has just created a new issue for https://github.com/webscreens/openscreenprotocol:

== [Control] Bidirectional control protocol ==
This is an editorial task to ensure that either endpoint of a control channel can assume either role in the Presentation API (or Remote Playback API, or any other API going forward).

Example:  Two controlling user agents are connected to a presentation receiver.  One starts presentation of a video with closed captions, and uses its control channel to request that the display push the closed captions to the second controller.

Note that this also implies that the underlying discovery/transport protocols should not constrain which device is the controlling UA and which is the receiver.  For example, the controlling UA could act as a QUIC server or mDNS responder for the purposes of establishing the control channel (even though current implementations typically go the other way).  There might be practical reasons this isn't common, but it should be possible.

There some more API and protocol level work required to make this work.  For example, when a control channel is established, part of the handshake should figure out whether each side can act as a controller, receiver or both.
 

Please view or discuss this issue at https://github.com/webscreens/openscreenprotocol/issues/61 using your GitHub account

Received on Monday, 9 October 2017 21:46:55 UTC