-
Wez authored
Previously CastRunner would look for Agent-provided services (e.g. CastChannel) in the service namespace supplied on component launch. If a ComponentContext is found in the service namespace passed to StartComponent() then the CastRunner will now use that to connect to the CastAgent to find Cast-specific services. This requires temporary work-arounds e.g. to fall-back to looking at the "additional services" provided in the component's StartupInfo, until we migrate to the new component-manager APIs. Bug: 920920, 893229 Change-Id: I43aec5c47bc24a0d2a537de621b20fad3342a5f8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1472333 Commit-Queue: Wez <wez@chromium.org> Reviewed-by:
Kevin Marshall <kmarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#638215}
4e3dbc1a