fdo-mirrors/dbus
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/dbus/dbus.git synced 2026-04-21 12:20:44 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

Upgrade the type system into its own top-level section of the spec

Browse source 
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>
This commit is contained in:
Simon McVittie 2011-04-26 17:37:21 +01:00
parent 0d7318ccc7
commit 23cb3ecad3
1 changed files with 30 additions and 19 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

49
doc/dbus-specification.xml
View file

@ -264,27 +264,13 @@
</sect1>
<sect1 id="message-protocol">
<title>Message Protocol</title>
<sect1 id="type-system">
<title>Type System</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 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>