tree: be0e51a5df4e1dbb08154e11c07795d7d2541def [path history] [tgz]
  1. DEPS
  2. OWNERS
  3. README.md
  4. ash_dbus_helper.cc
  5. ash_dbus_helper.h
  6. ash_dbus_services.cc
  7. ash_dbus_services.h
  8. display_service_provider.cc
  9. display_service_provider.h
  10. liveness_service_provider.cc
  11. liveness_service_provider.h
  12. org.chromium.DisplayService.conf
  13. org.chromium.LivenessService.conf
  14. org.chromium.UrlHandlerService.conf
  15. url_handler_service_provider.cc
  16. url_handler_service_provider.h
  17. url_handler_service_provider_unittest.cc
ash/dbus/README.md

Under classic/single-process mash:

  • The dbus::Bus instance is created in chrome and passed to ash in ShellInitParams.
  • Access to D-Bus clients is restricted to clients that will eventually be owned by the ash process.

Under multi-process ash (mash):

  • AshDBusHelper creates its own dbus thread and dbus::Bus instance.
  • The D-Bus clients created in AshService are owned by the ash process.
  • The D-Bus services in AshDBusServices are owned by the ash process.

See //ash/README.md for details on mash. See Chrome OS D-Bus Usage in Chrome for information about adding D-Bus services.