Specify that PreferredHandler trumps the filter

Clients requesting channels for themselves shouldn't have to jump
through hoops to do so, and if you request a channel for a particular
other application you'd better be sure it can deal with it.

1 files changed, 8 insertions, 1 deletions

diff --git a/spec/Channel_Dispatcher.xml b/spec/Channel_Dispatcher.xml
index 06f0458d..75362f3f 100644
--- a/spec/Channel_Dispatcher.xml
+++ b/spec/Channel_Dispatcher.xml
@@ -185,7 +185,9 @@
             channel, or an empty string to indicate that any handler would be
             acceptable. The channel dispatcher SHOULD dispatch as many as
             possible of the resulting channels (ideally, all of them)
-            to that handler, and SHOULD remember the preferred handler
+            to that handler—irrespective of whether that handler's <tp:dbus-ref
+              namespace="org.freedesktop.Telepathy.Client.Handler">HandlerChannelFilter</tp:dbus-ref>
+            matches the channel—and SHOULD remember the preferred handler
             so it can try to dispatch subsequent channels in the same bundle
             to the same handler.</p>
 
@@ -199,6 +201,11 @@
                 namespace="org.freedesktop.Telepathy.Client.Handler">HandleChannels</tp:dbus-ref>
               on it, and partly so the channel dispatcher
               can recover state if it crashes and is restarted.</p>
+
+            <p>The filter should be disregarded for ease of use of this
+              interface: clients will usually use this argument to request
+              channels be sent to themself, and this should trump the filter
+              not matching.</p>
           </tp:rationale>
 
           <p>If this is a well-known bus name and the handler has the