This directory contains Chrome Foundation Services. If you think of Chrome as a “portable OS,” Chrome Foundation Services can be thought of as that OS' foundational “system services” layer.
Roughly each subdirectory here corresponds to a service that:
//services/service_managerwith its own unique Identity.
Individual services are structured like so:
//services/foo/ <-- Implementation code, may have subdirs. /public/ /cpp/ <-- C++ client libraries (optional) /interfaces/ <-- Mojom interfaces
//services may only depend on each other via each other's
/public/ directories, i.e. implementation code may not be shared directly.
Service code should also take care to tightly limit the dependencies on static libraries from outside of
//services. Dependencies to large platform layers like
//third_party/WebKit must be avoided.
Note that while it may be possible to build a discrete physical package (DSO) for each service, products consuming these services may package them differently, e.g. by combining them into a single package.
Services can be thought of as integrators of library code from across the Chromium repository, most commonly
//mojo (obviously) but for each service also
//ui, etc. in accordance with the functionality they provide.
Not everything in
//components is automatically a service in its own right. Think of
//components as sort of like a
//components can define, implement and use Mojom interfaces, but only
//services have unique identities with the Service Manager and so only
//services make it possible for Mojom interfaces to be acquired.
See the Service Manager documentation for more details regarding how to define a service and expose or consume interfaces to and from other services.
Please start a thread on firstname.lastname@example.org if you want to introduce a new service.