1Under classic/single-process mash: 2* The dbus::Bus instance is created in chrome and passed to ash in 3 ShellInitParams. 4* Access to D-Bus clients is restricted to clients that will eventually be owned 5 by the ash process. 6 7Under multi-process ash (mash): 8* AshDBusHelper creates its own dbus thread and dbus::Bus instance. 9* The D-Bus clients created in AshService are owned by the ash process. 10* The D-Bus services in AshDBusServices are owned by the ash process. 11 12See `//ash/README.md` for details on mash. 13See [Chrome OS D-Bus Usage in Chrome] for information about adding D-Bus 14services. 15 16[Chrome OS D-Bus Usage in Chrome]: https://chromium.googlesource.com/chromiumos/docs/+/HEAD/dbus_in_chrome.md 17