summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/TODO11
-rw-r--r--doc/dbus-specification.sgml17
2 files changed, 20 insertions, 8 deletions
diff --git a/doc/TODO b/doc/TODO
index ebbff3ac..f6c539dd 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -48,3 +48,14 @@
- Abstract the user database, so you can use something other than the system password
database.
+
+ - The convenience functions in dbus-bus.h should perhaps have
+ the signatures that they would have if they were autogenerated
+ stubs. e.g. the acquire service function. We should also evaluate
+ which of these functions to include, in light of the fact that
+ GLib/Qt native stubs will probably also exist.
+
+ - The message handler interface needs rethinking, perhaps handlers should be able
+ to return an error that automatically gets turned into a message; most likely
+ some basic spec'ing out of the GLib/Qt level stubs/skels stuff will be
+ needed to understand the right approach.
diff --git a/doc/dbus-specification.sgml b/doc/dbus-specification.sgml
index 7e2fcb35..3c41068e 100644
--- a/doc/dbus-specification.sgml
+++ b/doc/dbus-specification.sgml
@@ -184,7 +184,7 @@
<tbody>
<row>
<entry>0x1</entry>
- <entry>This message is an error reply.</entry>
+ <entry>This message is an error reply. If the first argument exists and is a string, it is an error message.</entry>
</row>
</tbody>
</tgroup>
@@ -978,12 +978,13 @@
number of the message being replied to.
</para>
<para>
- If an error occurs, an error reply may be sent in place of the
- standard reply. Error replies can be identified by a special
- header flag, see <xref linkend="message-protocol-header-encoding">.
- Error replies have a name which reflects the type of
- error that occurred. Error replies would generally
- be mapped to exceptions in a programming language.
+ If an error occurs, an error reply may be sent in place of the standard
+ reply. Error replies can be identified by a special header flag, see
+ <xref linkend="message-protocol-header-encoding">. Error replies have a
+ name which reflects the type of error that occurred. Error replies would
+ generally be mapped to exceptions in a programming language. If an
+ error reply has a first argument, and that argument has type STRING,
+ then the argument must be an error message.
</para>
<para>
[FIXME discuss mapping of broadcast messages + matching rules
@@ -1220,7 +1221,7 @@
# Sample service description file
[D-BUS Service]
Name=org.gnome.ConfigurationDatabase
- Exec=gconfd-2
+ Exec=/usr/libexec/gconfd-2
</programlisting>
</figure>
</para>