We have several helpers for integrating Service Manager into the Content layer, including ServiceManagerConnection, ChildConnection, and ServiceManagerContext.

These have been useful but they've also lead to some redundant API surface between content and non-content code (and thus confusingly N>1 ways of doing some things), as well as a growing number of unwanted dependencies on the browser process's environment within ServiceManagerContext, where we plug in a lot of service registration gunk.

In the interest of supporting an out-of-process Service Manager (sans browser), as well as generally cleaning up SM integration across Content/Chrome, we should eliminate these helpers and migrate Content/Chrome code to directly use the few primitives made available by the Service Manager's client library.
 

We have several helpers for integrating Service Manager into the Content layer, including (all in src/content) ServiceManagerConnection, ChildConnection, and ServiceManagerContext.

These have been useful but they've also lead to some redundant API surface between content and non-content code (and thus confusingly N>1 ways of doing some things), as well as a growing number of unwanted dependencies on the browser process's environment within ServiceManagerContext, where we plug in a lot of service registration gunk.

In the interest of supporting an out-of-process Service Manager (sans browser), as well as generally cleaning up SM integration across Content/Chrome, we should eliminate these helpers and migrate Content/Chrome code to directly use the few primitives made available by the Service Manager's client library.