tree: c2716f7c7fb56ed237e7c1d251605435f9da0bab [path history] [tgz]
  1. ash_dbus_helper.cc
  2. ash_dbus_helper.h
  3. ash_dbus_services.cc
  4. ash_dbus_services.h
  5. DEPS
  6. display_service_provider.cc
  7. display_service_provider.h
  8. liveness_service_provider.cc
  9. liveness_service_provider.h
  10. org.chromium.DisplayService.conf
  11. org.chromium.LivenessService.conf
  12. org.chromium.UrlHandlerService.conf
  13. OWNERS
  14. README.md
  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.