From f1beb15144c90e27c6a6aa4c8544ed5cfd1d0210 Mon Sep 17 00:00:00 2001 From: Simon McVittie Date: Mon, 11 Dec 2017 18:40:36 +0000 Subject: [PATCH 1/7] spec: Allow non-message-bus servers to use SENDER and DESTINATION The Telepathy "Tubes" APIs are an example of a server that is not a message bus, but makes use of the sender and destination fields to provide broadly unique-connection-name-like semantics. Signed-off-by: Simon McVittie --- doc/dbus-specification.xml | 18 +++++++++++++----- 1 file changed, 13 insertions(+), 5 deletions(-) diff --git a/doc/dbus-specification.xml b/doc/dbus-specification.xml index 1ec07a59..edbf3f0f 100644 --- a/doc/dbus-specification.xml +++ b/doc/dbus-specification.xml @@ -1692,9 +1692,12 @@ 6 STRING optional - The name of the connection this message is intended for. - Only used in combination with the message bus, see - . + + The name of the connection this message is intended for. + This field is usually only meaningful in combination with + the message bus (see ), + but other servers may define their own meanings for it. + SENDER @@ -1702,8 +1705,13 @@ STRING optional Unique name of the sending connection. - The message bus fills in this field so it is reliable; the field is - only meaningful in combination with the message bus. + This field is usually only meaningful in combination with + the message bus, but other servers may define their own + meanings for it. + On a message bus, this header field is controlled by + the message bus, so it is as reliable and trustworthy + as the message bus itself. + SIGNATURE -- 2.15.1