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