- From: Mark Foltz (Google) via GitHub <sysbot+gh@w3.org>
- Date: Wed, 07 Oct 2020 21:09:05 +0000
- To: public-secondscreen@w3.org
From an Open Screen point of view, this sounds fine. The protocol allows multiple media resources to be sent with the remote playback start request, at which point the Open Screen receiver can use its own source selection logic to decide what to play. [Here is the relevant section of the protocol spec](https://w3c.github.io/openscreenprotocol/#remote-playback-api) (paragraph starting with "When section 6.2.4 says...") Of course, if the user agent isn't using the Open Screen protocol, then it can use whatever mechanism it has to negotiate with the remote playback device which source to play (like knowing that certain devices support certain sources or not). -- GitHub Notification of comment by mfoltzgoogle Please view or discuss this issue at https://github.com/w3c/remote-playback/issues/125#issuecomment-705195054 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 7 October 2020 21:09:06 UTC