Commit a124562d authored by Simon McVittie's avatar Simon McVittie

GDBusConnection: document that this object is (meant to be) thread-safe

Bug: https://bugzilla.gnome.org/show_bug.cgi?id=661992Signed-off-by: Simon McVittie's avatarSimon McVittie <simon.mcvittie@collabora.co.uk>
Reviewed-by: default avatarDavid Zeuthen <davidz@redhat.com>
parent a031baca
......@@ -148,6 +148,15 @@
* an D-Bus client, it is often easier to use the g_bus_own_name(),
* g_bus_watch_name() or g_dbus_proxy_new_for_bus() APIs.
*
* As an exception to the usual GLib rule that a particular object must not be
* used by two threads at the same time, #GDBusConnection's methods may be
* called from any thread<footnote>
* <para>
* This is so that g_bus_get() and g_bus_get_sync() can safely return the
* same #GDBusConnection when called from any thread.
* </para>
* </footnote>.
*
* Most of the ways to obtain a #GDBusConnection automatically initialize it
* (i.e. connect to D-Bus): for instance, g_dbus_connection_new() and
* g_bus_get(), and the synchronous versions of those methods, give you an
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment