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

Bug: https://bugzilla.gnome.org/show_bug.cgi?id=661992
Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk>
Reviewed-by: David Zeuthen <davidz@redhat.com>
This commit is contained in:
Simon McVittie 2011-10-21 11:42:10 +01:00
parent a031bacaac
commit a124562d1b

View File

@ -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