[Telepathy-commits] [telepathy-spec/master] ContactSearch: cross-reference SearchKeys property and rename it to AvailableSearchKeys
Simon McVittie
simon.mcvittie at collabora.co.uk
Tue Feb 17 05:42:32 PST 2009
Also explicitly say that it's immutable, for round-trip reduction.
---
spec/Channel_Type_Contact_Search.xml | 12 +++++++++---
1 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/spec/Channel_Type_Contact_Search.xml b/spec/Channel_Type_Contact_Search.xml
index 92e495a..0ac05b1 100644
--- a/spec/Channel_Type_Contact_Search.xml
+++ b/spec/Channel_Type_Contact_Search.xml
@@ -34,7 +34,8 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.</
from sending further results; if this is the case, it MUST ignore
any further results.</p>
- <p>Before searching, the AvailableSearchKeys property should be
+ <p>Before searching, the
+ <tp:member-ref>AvailableSearchKeys</tp:member-ref> property should be
inspected to determine the valid search keys which can be provided
to the Search method. A search request is then started by providing
some of these terms to the Search method, and the search status will
@@ -160,13 +161,18 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.</
</tp:docstring>
</tp:simple-type>
- <property name="SearchKeys" type="as" access="read"
- tp:name-for-bindings="Search_Keys">
+ <property name="AvailableSearchKeys" type="as" access="read"
+ tp:name-for-bindings="Available_Search_Keys">
<tp:docstring>
The set of search keys supported by this channel. Example values
include [""] (for protocols where several address fields are
implicitly searched) or ["x-n-given", "x-n-family", "nickname"]
(for XMPP XEP-0055, without extensibility via Data Forms).
+ This property cannot change during the lifetime of a channel.
+
+ <tp:rationale>
+ It can be in the NewChannels signal for round-trip reduction.
+ </tp:rationale>
</tp:docstring>
</property>
--
1.5.6.5
More information about the telepathy-commits
mailing list