summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorMatthias Clasen <mclasen@redhat.com>2010-05-09 12:24:56 -0400
committerMatthias Clasen <mclasen@redhat.com>2010-05-09 12:24:56 -0400
commitb96c3b6d60a87f31a46ff5499c133571f0470940 (patch)
treeb1c5f2ca88a91147774c0f26d16cfc3490802393 /docs
parentc148cafdd16f8bfed46cf5b0af05af3cbdc550c7 (diff)
Mention multithreading as a reason for not using libdbus
Diffstat (limited to 'docs')
-rw-r--r--docs/reference/gio/migrating-dbus-glib.xml4
1 files changed, 3 insertions, 1 deletions
diff --git a/docs/reference/gio/migrating-dbus-glib.xml b/docs/reference/gio/migrating-dbus-glib.xml
index 68202d53f..dc7aeaff1 100644
--- a/docs/reference/gio/migrating-dbus-glib.xml
+++ b/docs/reference/gio/migrating-dbus-glib.xml
@@ -13,7 +13,9 @@
<listitem><para>
dbus-glib uses libdbus, GDBus doesn't. Instead, it relies on GIO
streams as transport layer, and has its own implementation for the
- the D-Bus connection setup and authentication.
+ the D-Bus connection setup and authentication. Apart from using
+ streams as transport, avoiding libdbus also lets GDBus avoid some
+ thorny multithreading issues.
</para></listitem>
<listitem><para>
dbus-glib uses the GObject type system for method arguments and