tree: 220373ce766349cdc6220788f64f5e692562ef3e [path history] [tgz]
  1. chrome_features_service_provider.cc
  2. chrome_features_service_provider.h
  3. component_updater_service_provider.cc
  4. component_updater_service_provider.h
  5. cryptohome_key_delegate_service_provider.cc
  6. cryptohome_key_delegate_service_provider.h
  7. dbus_helper.cc
  8. dbus_helper.h
  9. drive_file_stream_service_provider.cc
  10. drive_file_stream_service_provider.h
  11. kiosk_info_service_provider.cc
  12. kiosk_info_service_provider.h
  13. libvda_service_provider.cc
  14. libvda_service_provider.h
  15. machine_learning_decision_service_provider.cc
  16. machine_learning_decision_service_provider.h
  17. metrics_event_service_provider.cc
  18. metrics_event_service_provider.h
  19. org.chromium.ChromeFeaturesService.conf
  20. org.chromium.ComponentUpdaterService.conf
  21. org.chromium.CryptohomeKeyDelegate.conf
  22. org.chromium.DriveFileStreamService.conf
  23. org.chromium.KioskAppService.conf
  24. org.chromium.LibvdaService.conf
  25. org.chromium.MachineLearningDecisionService.conf
  26. org.chromium.MetricsEventService.conf
  27. org.chromium.NetworkProxyService.conf
  28. org.chromium.PluginVmService.conf
  29. org.chromium.ScreenLockService.conf
  30. org.chromium.VirtualFileRequestService.conf
  31. org.chromium.VmApplicationsService.conf
  32. OWNERS
  33. plugin_vm_service_provider.cc
  34. plugin_vm_service_provider.h
  35. proxy_resolution_service_provider.cc
  36. proxy_resolution_service_provider.h
  37. proxy_resolution_service_provider_browsertest.cc
  38. proxy_resolution_service_provider_unittest.cc
  39. README.md
  40. screen_lock_service_provider.cc
  41. screen_lock_service_provider.h
  42. virtual_file_request_service_provider.cc
  43. virtual_file_request_service_provider.h
  44. vm_applications_service_provider.cc
  45. vm_applications_service_provider.h
chrome/browser/chromeos/dbus/README.md

This directory contains implementations of D-Bus services that are owned by Chrome (because they depend on functionality located within //chrome).

Please see Chrome OS D-Bus Usage in Chrome for information about adding D-Bus services.