tree: a76577a432176c7b6911393defe886011172515b [path history] [tgz]
  1. ash_dbus_services.cc
  2. ash_dbus_services.h
  3. DEPS
  4. display_service_provider.cc
  5. display_service_provider.h
  6. gesture_properties_service_provider.cc
  7. gesture_properties_service_provider.h
  8. gesture_properties_service_provider_unittest.cc
  9. liveness_service_provider.cc
  10. liveness_service_provider.h
  11. org.chromium.DisplayService.conf
  12. org.chromium.GesturePropertiesService.conf
  13. org.chromium.LivenessService.conf
  14. org.chromium.UrlHandlerService.conf
  15. org.chromium.UserAuthenticationService.conf
  16. OWNERS
  17. README.md
  18. url_handler_service_provider.cc
  19. url_handler_service_provider.h
  20. url_handler_service_provider_unittest.cc
  21. user_authentication_service_provider.cc
  22. user_authentication_service_provider.h
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.