From 09d635c2db892790040bf94de1fa084a9571f61a Mon Sep 17 00:00:00 2001 From: Simon McVittie Date: Tue, 31 Jan 2012 15:41:46 +0000 Subject: Align the canonical RCC for ContactSearch channels with our normal policy Bug: https://bugs.freedesktop.org/show_bug.cgi?id=32468 --- spec/Channel_Type_Contact_Search.xml | 14 ++++++-------- spec/Connection_Interface_Requests.xml | 6 +----- 2 files changed, 7 insertions(+), 13 deletions(-) diff --git a/spec/Channel_Type_Contact_Search.xml b/spec/Channel_Type_Contact_Search.xml index 3ca8bc71..2d8fa452 100644 --- a/spec/Channel_Type_Contact_Search.xml +++ b/spec/Channel_Type_Contact_Search.xml @@ -26,6 +26,9 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.x-telepathy-identifier. + + The requestable channel class now fixes TargetHandleType=NONE. +

A channel type for searching server-stored user directories. A new @@ -37,17 +40,12 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.RequestableChannelClasses with the ChannelType fixed to this - interface, and no other fixed properties. That requestable + interface, + TargetHandleType + fixed to Handle_Type_None, and no other fixed properties. That requestable channel class MAY also have the Server and Limit properties in its list of allowed properties, depending on the protocol.

- -

The requestable channel class would normally also have TargetHandleType fixed to - None, but the initial implementation of ContactSearch - (in telepathy-gabble) didn't do this.

-
-

All channels of this type should have TargetHandleType None (and hence Channel classes SHOULD always include the keys im.telepathy1.Channel.ChannelType and - im.telepathy1.Channel.TargetHandleType. - (One exception is that ContactSearch1 channels do not have TargetHandleType - None in their requestable channel classes, for - historical reasons.)

+ im.telepathy1.Channel.TargetHandleType.

-- cgit v1.2.3