Mention D-Bus functionality in the overview

This commit is contained in:
Matthias Clasen 2010-05-06 18:15:00 -04:00
parent 133f66538d
commit f14e30818c

View File

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