[MBI] Always associate AgentSchedulingGroupHost with AgentSchedulingGroup.
Regardless of whether we are in "MBI mode" or "legacy mode", the AgentSchedulingGroup and AgentSchedulingGroupHost interfaces should be associated with one another. This is because we want to preserve the current behavior, where all channel-associated interfaces are all bound to the same pipe and not separated by the direction (browser->renderer or renderer->browser). This CL moves the binding of the ASGH interface to the method that was used to bind the RouteProvider interfaces (and renames it appropriately). Bug: 1111231 Change-Id: I4304e00a65b44d11f5dad6fb51ec1bedde76ec26 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2528813 Commit-Queue: Tal Pressman <talp@chromium.org> Reviewed-by:Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Dominic Farolino <dom@chromium.org> Cr-Commit-Position: refs/heads/master@{#827139}
Showing
Please register or sign in to comment