From a124562d1bdd51de4b136725b3902b1e518d991f Mon Sep 17 00:00:00 2001 From: Simon McVittie Date: Fri, 21 Oct 2011 11:42:10 +0100 Subject: [PATCH] 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 Reviewed-by: David Zeuthen --- gio/gdbusconnection.c | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/gio/gdbusconnection.c b/gio/gdbusconnection.c index 1b01624..76701e6 100644 --- a/gio/gdbusconnection.c +++ b/gio/gdbusconnection.c @@ -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 + * + * This is so that g_bus_get() and g_bus_get_sync() can safely return the + * same #GDBusConnection when called from any thread. + * + * . + * * 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 -- 2.7.4