chromium/src
0
Fork 0
Code Activity

dbus: Update comment of ObjectProxy::WaitForServiceToBeAvailable

Browse Source 
It is important to make clear that callbacks are executed in which
thread.

As ObjectProxy::RunWaitForServiceToBeAvailableCallbacks() asserts at its
first line, WaitForServiceToBeAvailableCallback are called in the origin
thread.

Bug: none
Change-Id: I8e90254edc75040f08ecca48c3227e82ff26f1b9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5340776
Reviewed-by: Hidehiko Abe <hidehiko@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Commit-Queue: Shin Kawamura <kawasin@google.com>
Cr-Commit-Position: refs/heads/main@{#1268883}
This commit is contained in:
Shintaro Kawamura
2024-03-06 04:14:09 +00:00
committed by Chromium LUCI CQ
parent 8c412864e7
commit 1d3f42a27d
1 changed files with 3 additions and 1 deletions

4
dbus/object_proxy.h

@ -203,7 +203,9 @@ class CHROME_DBUS_EXPORT ObjectProxy
// service is already available, or if connecting to the name-owner-changed
// signal fails, |callback| will be run once asynchronously. Otherwise,
// |callback| will be run once in the future after the service becomes
// available.
// available. |callback| will be called in the origin thread in either case.
//
// Must be called in the origin thread.
virtual void WaitForServiceToBeAvailable(
WaitForServiceToBeAvailableCallback callback);