diff options
| author | Simon McVittie <simon.mcvittie@collabora.co.uk> | 2011-04-26 17:37:21 +0100 |
|---|---|---|
| committer | Simon McVittie <simon.mcvittie@collabora.co.uk> | 2011-07-28 12:18:50 +0100 |
| commit | 23cb3ecad32a3ea90ebc36cba22b829136322c20 (patch) | |
| tree | 29b393a6f44969ce32825612226d4ab2c8c57594 /doc | |
| parent | 0d7318ccc72b0b984a3a27e71eb5e9a3919ff3bb (diff) | |
| download | dbus-23cb3ecad32a3ea90ebc36cba22b829136322c20.tar.gz | |
Upgrade the type system into its own top-level section of the spec
The type system can be used independently, for instance in GVariant
(although GVariant's binary encoding is in fact not the same).
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=38252
Reviewed-by: Lennart Poettering <lennart@poettering.net>
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/dbus-specification.xml | 49 |
1 files changed, 30 insertions, 19 deletions
diff --git a/doc/dbus-specification.xml b/doc/dbus-specification.xml index 4bd0cb32..54f9049d 100644 --- a/doc/dbus-specification.xml +++ b/doc/dbus-specification.xml @@ -264,27 +264,13 @@ </sect1> - <sect1 id="message-protocol"> - <title>Message Protocol</title> - - <para> - A <firstterm>message</firstterm> consists of a - <firstterm>header</firstterm> and a <firstterm>body</firstterm>. If you - think of a message as a package, the header is the address, and the body - contains the package contents. The message delivery system uses the header - information to figure out where to send the message and how to interpret - it; the recipient interprets the body of the message. - </para> - - <para> - The body of the message is made up of zero or more - <firstterm>arguments</firstterm>, which are typed values, such as an - integer or a byte array. - </para> + <sect1 id="type-system"> + <title>Type System</title> <para> - Both header and body use the same type system and format for - serializing data. Each type of value has a wire format. + D-Bus has a type system, in which values of various types can be + serialized into a sequence of bytes referred to as the + <firstterm>wire format</firstterm> in a standard way. Converting a value from some other representation into the wire format is called <firstterm>marshaling</firstterm> and converting it back from the wire format is <firstterm>unmarshaling</firstterm>. @@ -843,6 +829,31 @@ </sect2> + </sect1> + + <sect1 id="message-protocol"> + <title>Message Protocol</title> + + <para> + A <firstterm>message</firstterm> consists of a + <firstterm>header</firstterm> and a <firstterm>body</firstterm>. If you + think of a message as a package, the header is the address, and the body + contains the package contents. The message delivery system uses the header + information to figure out where to send the message and how to interpret + it; the recipient interprets the body of the message. + </para> + + <para> + The body of the message is made up of zero or more + <firstterm>arguments</firstterm>, which are typed values, such as an + integer or a byte array. + </para> + + <para> + Both header and body use the D-Bus <link linkend="type-system">type + system</link> and format for serializing data. + </para> + <sect2 id="message-protocol-messages"> <title>Message Format</title> |