GitLab

ContentBrowserClient::WillStartServiceManager exists exclusively to
initialize some Audio Service policy state very early in browser
lifetime. This was necessary at one point because the Service Manager
was a prerequisite for various service bits to be configured, and
Service Manager bringup happens very early in startup.

Because the Service Manager is no longer used to host the Audio Service,
the service is free to manage its own configuration independently. It
can instead now query the sandboxing policy on-demand when launching the
service process, eliminating any need for a ContentBrowserClient API.

This also deletes the unused ShouldTerminateOnServiceQuit
ContentBrowserClient API, as well as its supporting code within Service
Manager.

Bug: 977637
Change-Id: I3fa148cf4ceb9bb26f56e2b736d20a6cce2170dc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2538333
Commit-Queue: Ken Rockot <rockot@google.com>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#827551}