chromium/src
0
Fork 0
Code Activity

docs: Remove tokens in D-Bus MojoConnectionService Provider doc

Browse Source 
BUG=b:181831555
TEST=viewed the md on Google Chrome locally

Change-Id: Ice91109c0183677b0c0a49cbb4133de0f679b845
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2738897
Reviewed-by: Mike Pinkerton <pinkerton@chromium.org>
Commit-Queue: Cheng-Hao Yang <chenghaoyang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#861056}
This commit is contained in:
Harvey Yang
2021-03-09 07:37:50 +00:00
committed by Chromium LUCI CQ
parent 9ba6669ede
commit 8e23bb1b28
1 changed files with 3 additions and 3 deletions

6
docs/dbus_mojo_connection_service.md

@ -12,7 +12,7 @@ D-Bus Mojo Connection Service lives in [//chrome/browser/chromeos/dbus/mojo_conn
Follow the example of CrOS Sensors' [changelist](https://chromium-review.googlesource.com/c/chromium/src/+/2352298).
### Steps to Add a usage for a CrOS process with a new D-Bus method:
1. Add a method name & a well-known token in both CrOS platform and Chrome.
1. Add a method name in both CrOS platform and Chrome.
(Recommend: `platform2/system_api`)
2. Add the busconfig policy in [MojoConnectionService.conf].
3. Upon a D-Bus request coming from the CrOS service, pass one endpoint of the
@ -28,8 +28,8 @@ to generate the pipe.
### Steps to Add a usage for a CrOS process with an existing D-Bus method:
1. Add the busconfig policy in [MojoConnectionService.conf].
And that’s it. The method name, token and the logic in the service provider can
be reused.
And that’s it. The method name and the logic in the service provider can be
reused.
## Security