From d76937e2e1bfc8e30377468db1e190f92d081ef9 Mon Sep 17 00:00:00 2001 From: Havoc Pennington Date: Mon, 7 Feb 2005 04:47:52 +0000 Subject: 2005-02-06 Havoc Pennington * s/expected/required/ in a couple places for clarity --- doc/dbus-specification.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'doc') diff --git a/doc/dbus-specification.xml b/doc/dbus-specification.xml index b8a83814..9fc7b0f9 100644 --- a/doc/dbus-specification.xml +++ b/doc/dbus-specification.xml @@ -7,8 +7,8 @@
D-BUS Specification - Version 0.10 - 28 January 2005 + Version 0.11 + 6 February 2005 Havoc @@ -1031,7 +1031,7 @@ messages map naturally to methods on objects in a typical program. - A method call message is expected to have a MEMBER header field + A method call message is required to have a MEMBER header field indicating the name of the method. Optionally, the message has an INTERFACE field giving the interface the method is a part of. In the absence of an INTERFACE field, if two interfaces on the same object have @@ -1048,7 +1048,7 @@ to receive the message. - When an application handles a method call message, it is expected to + When an application handles a method call message, it is required to return a reply. The reply is identified by a REPLY_SERIAL header field indicating the serial number of the METHOD_CALL being replied to. The reply can have one of two types; either METHOD_RETURN or ERROR. @@ -1062,7 +1062,7 @@ Even if a method call has no return values, a METHOD_RETURN - reply is expected, so the caller will know the method + reply is required, so the caller will know the method was successfully processed. -- cgit