[glib/gdbus-merge] Mention D-Bus functionality in the overview

[Matthias Clasen <matthiasc src gnome org>]

commit f14e30818c7d355f0c3d61bab2f2a702dc747952
Author: Matthias Clasen <mclasen redhat com>
Date:   Thu May 6 18:15:00 2010 -0400

    Mention D-Bus functionality in the overview

 docs/reference/gio/overview.xml |   39 +++++++++++++++++++++++++++------------
 1 files changed, 27 insertions(+), 12 deletions(-)
---
diff --git a/docs/reference/gio/overview.xml b/docs/reference/gio/overview.xml
index 613538e..1c14666 100644
--- a/docs/reference/gio/overview.xml
+++ b/docs/reference/gio/overview.xml
@@ -105,6 +105,31 @@
           <listitem><para>network connection stream</para></listitem>
        </varlistentry>
     </variablelist>
+    There is support for connecting to D-Bus, sending and receiving
+    messages, owning and watching bus names, and making objects
+    available on the bus:
+    <variablelist>
+       <varlistentry>
+          <term>GDBusConnection</term>
+          <listitem><para>a D-Bus connection</para></listitem>
+       </varlistentry>
+
+       <varlistentry>
+          <term>GDBusMethodInvocation</term>
+          <listitem><para>for handling remove calls</para></listitem>
+       </varlistentry>
+
+       <varlistentry>
+          <term>GDBusServer</term>
+          <listitem><para>helper for accepting connections</para></listitem>
+       </varlistentry>
+
+       <varlistentry>
+          <term>GDBusProxy</term>
+          <listitem><para>proxy to access D-Bus interfaces on a remote object</para></listitem>
+       </varlistentry>
+
+    </variablelist>
     Beyond these, GIO provides facilities for file monitoring,
     asynchronous I/O and filename completion. In addition to the
     interfaces, GIO provides implementations for the local case.
@@ -254,8 +279,8 @@
       <para>
         This variable can be set to the name of a #GSettingsBackend
         implementation to override the default for debugging purposes.
-        The keyfile-based implementation that is included in GIO has
-        the name "keyfile", the one in dconf has the name "dconf-settings".
+        The memory-based implementation that is included in GIO has
+        the name "memory", the one in dconf has the name "dconf-settings".
       </para>
     </formalpara>
 
@@ -269,16 +294,6 @@
         for compiled schemas for #GSettings.
       </para>
     </formalpara>
-
-    <formalpara>
-      <title><envar>GSETTINGS_KEYFILE_BACKEND_STORE</envar></title>
-
-      <para>
-        This variable can be set to the path where the keyfile #GSettings
-        backend stores its data. By default, the keyfile is stored in
-        <filename>$HOME/.config/gsettings/store</filename>.
-      </para>
-    </formalpara>
   </chapter>
 
   <chapter id="extending-gio">