New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 848014 link

Starred by 2 users
Status: Closed
Owner:
█ guohuideng@chromium.org
Last visit > 30 days ago
Closed: Aug 3
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

unifying the way the media backend/device is identified within chromecast

Project Member Reported by guohuideng@chromium.org, May 30 2018 
There are two types of |HostedRendererType|(see /media/mojo/interfaces/interface_factory.mojom) that chromecast uses: |kDefault| and |kCastWebAppService|.

When |kDefault| is used, |type_specific_id| in |InterfaceFactory::CreateRenderer(...)| is an "audio device ID"
, while when |kCastWebAppService| is used, said |type_specific_id| is an "application session ID"

The use of the combination of |kDefault| and "audio device ID" can be replaced by the other, to simplify the code.

Comment 1 by benhenry@chromium.org, Aug 3

Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".

Comment 2 by guohuideng@chromium.org, Aug 3 

The planed CL didn't land so the issue should be deleted.

Comment 3 by guohuideng@chromium.org, Aug 3

Status: Closed (was: Assigned)
►

Sign in to add a comment