summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorSimon McVittie <simon.mcvittie@collabora.co.uk>2011-07-21 16:14:02 +0100
committerSimon McVittie <simon.mcvittie@collabora.co.uk>2011-07-29 16:29:49 +0100
commit80989477ddc122063070fa48c0e0e0b411b66cdc (patch)
tree2cd1b8477904acceb2012db924594ed11bffffa5 /doc
parent6e03e0ee35ee4cce9a7415427ccd5bed163e7d45 (diff)
downloaddbus-80989477ddc122063070fa48c0e0e0b411b66cdc.tar.gz
spec: make the Match Rules section true again
The spec previously claimed that only messages matching the client's match rules would be received. This is not actually true: messages listing a client as their DESTINATION are always delivered (security policy permitting). Bug: https://bugs.freedesktop.org/show_bug.cgi?id=39450 Reviewed-by: Thiago Macieira <thiago@kde.org>
Diffstat (limited to 'doc')
-rw-r--r--doc/dbus-specification.xml21
1 files changed, 13 insertions, 8 deletions
diff --git a/doc/dbus-specification.xml b/doc/dbus-specification.xml
index 54f9049d..3e8f8ec9 100644
--- a/doc/dbus-specification.xml
+++ b/doc/dbus-specification.xml
@@ -3857,14 +3857,19 @@
<sect3 id="message-bus-routing-match-rules">
<title>Match Rules</title>
<para>
- An important part of the message bus routing protocol is match
- rules. Match rules describe what messages can be sent to a client
- based on the contents of the message. When a message is routed
- through the bus it is compared to clients' match rules. If any
- of the rules match, the message is dispatched to the client.
- If none of the rules match the message never leaves the bus. This
- is an effective way to control traffic over the bus and to make sure
- only relevant message need to be processed by the client.
+ An important part of the message bus routing protocol is match
+ rules. Match rules describe the messages that should be sent to a
+ client, based on the contents of the message. Broadcast signals
+ are only sent to clients which have a suitable match rule: this
+ avoids waking up client processes to deal with signals that are
+ not relevant to that client.
+ </para>
+ <para>
+ Messages that list a client as their <literal>DESTINATION</literal>
+ do not need to match the client's match rules, and are sent to that
+ client regardless. As a result, match rules are mainly used to
+ receive a subset of broadcast signals.
+ </para>
</para>
<para>
Match rules are added using the AddMatch bus method