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 <withnall@endlessm.com>
Signed-off-by: Simon McVittie <smcv@collabora.com>
This commit is contained in:
Simon McVittie 2017-12-11 18:40:36 +00:00
parent 8e0a90e59f
commit 1769e9b65b

View file

@ -1692,9 +1692,12 @@
<entry>6</entry>
<entry><literal>STRING</literal></entry>
<entry>optional</entry>
<entry>The name of the connection this message is intended for.
Only used in combination with the message bus, see
<xref linkend="message-bus"/>.</entry>
<entry>
The name of the connection this message is intended for.
This field is usually only meaningful in combination with
the message bus (see <xref linkend="message-bus"/>),
but other servers may define their own meanings for it.
</entry>
</row>
<row>
<entry><literal>SENDER</literal></entry>
@ -1702,8 +1705,13 @@
<entry><literal>STRING</literal></entry>
<entry>optional</entry>
<entry>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.</entry>
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.
</entry>
</row>
<row>
<entry><literal>SIGNATURE</literal></entry>