[glib/gdbus-merge] Mention multithreading as a reason for not using libdbus
- From: Matthias Clasen <matthiasc src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [glib/gdbus-merge] Mention multithreading as a reason for not using libdbus
- Date: Sun, 9 May 2010 16:26:46 +0000 (UTC)
commit b96c3b6d60a87f31a46ff5499c133571f0470940
Author: Matthias Clasen <mclasen redhat com>
Date: Sun May 9 12:24:56 2010 -0400
Mention multithreading as a reason for not using libdbus
docs/reference/gio/migrating-dbus-glib.xml | 4 +++-
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 68202d5..dc7aeaf 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
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]