Re: [w3ctag/design-reviews] Media Capabilities (#218)

I think there's a need to support remote playback capabilities. The Remote Playback API [describes](https://w3c.github.io/remote-playback/#introduction) three modes of operation: media mirroring, media remoting, and media flinging.

In cases where the UA is requesting media content to pass through to a remote playback device (media mirroring and media remoting), you'd want to use the capabilities of the remote playback device to decide which media encoding to request from the server. So capability discovery is something we'd want to consider in the [Open Screen Protocol](https://github.com/webscreens/openscreenprotocol) design.

Discussion in the Second Screen WG so far has focused mainly on the media flinging case, where the remote playback device is typically handed the URL of the media, so would do its own negotiation with the server, so maybe here there's less of a need to expose the remote device capabilities? I'd need to think about this some more to be more certain though.

cc @mfoltzgoogle

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/218#issuecomment-453275368