Note from internal bug regarding device description fetching: If we can't get device description from a DIAL device due to a permanent error (e.g., 404, invalid) then we should cache that result similar to how we cache device descriptions, so that we don't keep re-querying and failing.
Labels: -Type-Bug -M-67 M-68 Type-Feature Status: Started (was: Assigned)
More notes from deduped bug:
Some points of discussion for the implementation and TODOs beyond the initial implementation:
- Simplify the use of route ID to simply the presentation ID
- Support timeouts for app launch / stop requests
- Metrics
- Investigate the use of PresentationConnection so that the DialMediaRouteProvider can communicate directly with the SDK client in the web page. This is a larger change that affects other MRPs that use the Presentation API.
This is feature complete per bug 816628 , but points above still need to be addressed:
- Simplify the use of route ID to simply the presentation ID
- Metrics
- Use of PresentationConnection
- Use of data_decoder service to parse Cast SDK messages
Re c#12: I consider the following blocking:
- Metrics
- Use of data_decoder service to parse Cast SDK messages
The following are not blocking but are nice to have:
- Simplify the use of route ID to simply the presentation ID
- Use of PresentationConnection
I will use this bug to track the implementation of these items.
Comment 1 by zhaobin@chromium.org
, Feb 3 2018