New issue
Advanced search Search tips

Issue 882481 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

[Media Router] Deprecate ConnectRouteByRouteId and route querying

Project Member Reported by imch...@chromium.org, Sep 10

Issue description

As part of the harmony UX rollout, we are also removing the join feature in the MR dialog. There are 2 items we can simplify / remove:

- There won't be a need for supporting the sourceId parameter in a route query. It was used by the dialog to determine what routes are joinable with the sourceId. As a bonus, since the route query will become parameter-less with the change, we can consider removing the route query API and just always have MediaRouteProvider implementations supply route updates.

- ConnectRouteByRouteId, the MediaRouter API used by the MR dialog to implement join, can be deprecated / removed with the harmony UX rollout. Although there were plans to actually replace JoinRoute with ConnectRouteByRouteId, we need to work out how the Cast autojoin will work with the new API. The simplest, though hacky way would be for MediaRouter to check for the "autojoin" presentation ID and a Cast presentation URL.
 
This will greatly simplify the MR API and implemenation.

Long term we should strive to deprecate the autojoin ID as it's not part of the Presentation API spec and is another barrier to interop.  But that's a separate change that will need its own design.


The Android media router APIs are planned to enable media display and playback on these secondary devices. Android apps that apply the media router API should add a Cast button as part of their user interface, to permit, users to pick a media route to play media on a  lower output device.
visit https://www.belkinroutersupportnumber.com/belkin-n300-router/ for Belkin router issues

Sign in to add a comment