W3C home > Mailing lists > Public > public-secondscreen@w3.org > April 2017

Re: [remote-playback] Interoperability concerns by lack of a common denominator in transport

From: Mounir Lamouri via GitHub <sysbot+gh@w3.org>
Date: Tue, 11 Apr 2017 10:34:26 +0000
To: public-secondscreen@w3.org
Message-ID: <issue_comment.created-293218289-1491906864-sysbot+gh@w3.org>
Thanks for the feedback @cynthia. The open screen protocol that @mfoltzgoogle is working on is indeed one of the solution we are considering for this interoperability issue.

This said, the Remote Playback API completely abstracts the protocol to the web developer contrary to the Presentation API. That means that websites will not have to do sniffing and will only be told that there is or is not available devices depending on the user's setup. Because of this, we believe that the Remote Playback API will offer a good interoperability story for the platform. In other words, if the browser supports Chrome Cast, and the user has a one in its network, the API will reflect that the device is available but the page doesn't need to know the Cast protocol. If the user switches to a browser that only handles AirPlay, the API on this browser will report no available device. The interop issue will mostly be for the user as changing browser might provide a different experience depending on their hardware setup.

GitHub Notification of comment by mounirlamouri
Please view or discuss this issue at https://github.com/w3c/remote-playback/issues/74#issuecomment-293218289 using your GitHub account
Received on Tuesday, 11 April 2017 10:34:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 11 April 2017 10:34:32 UTC