diff options
| author | Havoc Pennington <hp@redhat.com> | 2006-10-21 17:08:08 +0000 |
|---|---|---|
| committer | Havoc Pennington <hp@redhat.com> | 2006-10-21 17:08:08 +0000 |
| commit | afa4ffbd852686633086569cd34942917c5c49af (patch) | |
| tree | 5b7919a3255aac947f1a4ef130bafadb508db3a9 /doc | |
| parent | 65fcbd62876f435f08bbcb6ff4596545b8c87bbd (diff) | |
2006-10-21 Havoc Pennington <hp@redhat.com>
* dbus/dbus-message.h: put #ifndef DBUS_DISABLE_DEPRECATED around
dbus_message_iter_get_array_len().
* throughout: documentation improvements.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/dbus-specification.xml | 12 |
1 files changed, 8 insertions, 4 deletions
diff --git a/doc/dbus-specification.xml b/doc/dbus-specification.xml index 41d3fb9b..977734d7 100644 --- a/doc/dbus-specification.xml +++ b/doc/dbus-specification.xml @@ -1184,7 +1184,8 @@ A signal emission is simply a single message of type <literal>SIGNAL</literal>. It must have three header fields: <literal>PATH</literal> giving the object the signal was emitted from, plus <literal>INTERFACE</literal> and <literal>MEMBER</literal> giving - the fully-qualified name of the signal. + the fully-qualified name of the signal. The <literal>INTERFACE</literal> header is required + for signals, though it is optional for method calls. </para> </sect3> @@ -3014,7 +3015,9 @@ <entry><literal>interface</literal></entry> <entry>An interface name (see <xref linkend="message-protocol-names-interface"/>)</entry> <entry>Match messages sent over or to a particular interface. An example of an - interface match is interface='org.freedesktop.Hal.Manager'</entry> + interface match is interface='org.freedesktop.Hal.Manager'. + If a message omits the interface header, it must not match any rule + that specifies this key.</entry> </row> <row> <entry><literal>member</literal></entry> @@ -3035,12 +3038,13 @@ example of a destination match is destination=':1.0'</entry> </row> <row> - <entry><literal>arg[1, 2, 3, ...]</literal></entry> + <entry><literal>arg[0, 1, 2, 3, ...]</literal></entry> <entry>Any string</entry> <entry>Arg matches are special and are used for further restricting the match based on the arguments in the body of a message. As of this time only string arguments can be matched. An example of an argument match - would be arg3='Foo'.</entry> + would be arg3='Foo'. Only argument indexes from 0 to 63 should be + accepted.</entry> </row> </tbody> </tgroup> |