From: Simon McVittie Date: Mon, 11 Dec 2017 18:40:36 +0000 (+0000) Subject: spec: Allow non-message-bus servers to use SENDER and DESTINATION X-Git-Tag: dbus-1.13.0~39 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=1769e9b65ba9b344823316d439bb90c771d1f90b;p=thirdparty%2Fdbus.git 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. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=100317 Reviewed-by: Philip Withnall Signed-off-by: Simon McVittie --- diff --git a/doc/dbus-specification.xml b/doc/dbus-specification.xml index 6e42839cb..8e3853519 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