From 9c5d01f0fe1ba855c0f7518c4f27d75a609b8faa Mon Sep 17 00:00:00 2001 From: Havoc Pennington Date: Sat, 2 Aug 2003 03:39:35 +0000 Subject: 2003-08-01 Havoc Pennington * dbus/dbus-object-registry.c (_dbus_object_registry_handle_and_unlock): implement * dbus/dbus-message.c (dbus_message_get_type): new function * doc/dbus-specification.sgml: add "type" byte to messages --- doc/dbus-specification.sgml | 58 +++++++++++++++++++++++++++++++++++++++------ 1 file changed, 51 insertions(+), 7 deletions(-) (limited to 'doc/dbus-specification.sgml') diff --git a/doc/dbus-specification.sgml b/doc/dbus-specification.sgml index 68a71cec..a53be53d 100644 --- a/doc/dbus-specification.sgml +++ b/doc/dbus-specification.sgml @@ -133,6 +133,12 @@ Endianness flag; ASCII 'l' for little-endian or ASCII 'B' for big-endian. + + 1 byte + Type of message. Unknown types MUST be ignored. + Currently-defined types are described below. + + 1 byte Bitwise OR of flags. Unknown flags @@ -148,12 +154,6 @@ version for this version of the specification is 0. - - 1 byte - A nul byte, reserved for future use. - Any value for this byte MUST be accepted. - - 4 bytes An unsigned 32-bit integer in the @@ -182,7 +182,44 @@ - Flags that can appear in the second byte of the header: + Types that can appear in the second byte of the header: + + + + + Decimal value + Description + + + + + 0 + This is an invalid type, if seen in a message + the connection should be dropped immediately. + + + 1 + Method call. + + + + 2 + Method reply with returned data. + + + 3 + Error. + + + 4 + Signal emission. + + + + + + + Flags that can appear in the third byte of the header: @@ -196,6 +233,13 @@ 0x1 This message is an error reply. If the first argument exists and is a string, it is an error message. + + 0x2 + This message does not expect method return replies or + error replies; the reply can be omitted as an + optimization. However, it is compliant with this specification + to return the reply despite this flag. + -- cgit