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

Issue 698938 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 2
Type: Bug



Sign in to add a comment

[Cast] Implement dual discovery in CastMediaSinkService

Project Member Reported by imch...@chromium.org, Mar 7 2017

Issue description

The current Cast sink discovery tries to resolve Cast device discovered by DIAL to improve overall reliability. This bug tracks the porting of such logic to the browser / CastMediaSinkService.

Sketch implementation:
(1) Add a callback mechanism to notify CastMediaSinkService of devices discovered by DialMediaSinkService.
(2) Deduplicate with the current list of sinks. If device is new, try to resolve the device by opening a Cast channel.
(3) If successful, add sink to current sink list.

Note an optimization can be made during (2) to skip non-Cast devices. This involves patching the Cast receiver library to advertise that it is a Cast device during DIAL discovery. This optimization can b edone later.
 

Comment 1 by mfo...@chromium.org, Oct 26 2017

Cc: -zhaobin@chromium.org
Labels: M-63
Owner: zhaobin@chromium.org
Status: Fixed (was: Available)
I believe this has been implemented.

Comment 2 by mfo...@chromium.org, Oct 26 2017

Components: -Blink>PresentationAPI Internals>Cast>API

Sign in to add a comment