From: Simon McVittie Date: Thu, 21 Jul 2011 15:14:02 +0000 (+0100) Subject: spec: make the Match Rules section true again X-Git-Tag: dbus-1.5.6~5 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=80989477ddc122063070fa48c0e0e0b411b66cdc;p=thirdparty%2Fdbus.git 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 --- diff --git a/doc/dbus-specification.xml b/doc/dbus-specification.xml index 54f9049dd..3e8f8ec91 100644 --- a/doc/dbus-specification.xml +++ b/doc/dbus-specification.xml @@ -3857,14 +3857,19 @@ Match Rules - 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. + + + Messages that list a client as their DESTINATION + 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. + Match rules are added using the AddMatch bus method