| Home | Trees | Indices | Help |
|
|---|
|
|
object --+
|
skypekit.Cached --+
|
skypekit.Object --+
|
ContactSearch
This class encapsulates functionality for looking up contacts on the Skype network. Contacts can be searched by portion of their name, e-mail address, language preferences, etc.
Contact search is asynchronous. ContactSearch::Submit is a non-blocking function that initiates the search. Upon finding a matching contact, ContactSearch::OnNewResult event gets fired, that gives you the reference to the discovered contact. You can get up to 100 matching contacts per search. Note that you will need to keep a live reference of the ContactSearch object while the search is doing its work.
So, to perform a contact search:
When the search has done its job, the ContactSearch::P_CONTACT_SEARCH_STATUS property will go to one of the terminal values.
The terminal values are:
There are three methods to create the ContactSearch objects.
A) Skype::CreateIdentitySearch
This method takes a string argument and looks for exact matches against Contact::P_SKYPENAME property. So for example, identity search for "echo" will return 0 results and search for "echo123" will return exactly one.
Identity in this case means skypename - contact search does not work with PSTN type contacts. However, it does work for SKYPE type contacts that have supplied P_PHONE_HOME, P_PHONE_OFFICE or P_PHONE_MOBILE values in their account data. To search for those, you will need to use complex search (see below).
Note that you should always check for boolean return value of the CreateIdentitySearch method. If the user submits a string that is not a valid skypename, the method will return false and the ContactSearchRef argument will return as NULL.
B) Skype::CreateBasicContactSearch
This method takes a string argument and looks for non-exact matches against both P_SKYPENAME and P_FULLNAME properties of the contact. If you intend to implement a simple, one-input search feature - this is the best method for you. The non-exact matching operates similarly to the SQL LIKE condition.
C) Skype::CreateContactSearch
This method enables you to implement advanced contact search, matching against multiple seach criteria. It takes no input arguments and expects search criteria to be added to the already constructed search object.
Criteria can be added with ContactSearch::AddStrTerm and ContactSearch::AddIntTerm methods.
These methods take Contact class porperty ID, condition, and the match pattern as inputs.
Only the following Contact properties can be used for search:
String searches are case insensitive, i.e. search for echo123 also matches ECHO123
When adding multiple criteria, default behaviour is that the criterions are additive. I.e. a term skypename == "joe" followed by term country == "us" will result in intersection between all joes and everybody in US.
You can explicitly add an "OR" instead of "AND" between conditions, using the AddOr method.
By default, AND criteria are grouped together, before OR's, so that:
AddTerm(condition1) AddTerm(condition2) AddOr() AddTerm(condition3) AddTerm(condition4)
will result in the following logical statement: (condition1 AND condition2) OR (condition3 AND condition4)
However, you can add "global" critera, by using the add_to_subs argument of the AddXX methods.
AddTerm(condition1) AddTerm(condition2) AddOr() AddTerm(condition3) AddTerm(condition4, add_to_subs=true)
which would result in: (condition1 AND condition2 AND condition4) OR (condition3 AND condition4)
Every one of the contact properties can only be used once, per search. For example, you cannot create a search for two different P_FULLNAME patterns. The &valid argument will still return tue if you do this, but the last criteria for any given property will override all previous ones. So, a search like this:
cs->AddStrTerm(Contact::P_FULLNAME, ContactSearch::EQ, "John Smith", isValid); cs->AddOr(); cs->AddStrTerm(Contact::P_FULLNAME, ContactSearch::EQ, "Ivan Sidorov", isValid);
will only return matches for "Ivan Sidorov" and none for "John Smith".
Some of the contact properties are automatically combined for purposes of search.
A search for P_SKYPENAME also returns matches from the P_FULLNAME property and vice versa.
So that this: cs->AddStrTerm(Contact::P_SKYPENAME, ContactSearch::EQ, "john.smith", isValid);
..and this: cs->AddStrTerm(Contact::P_FULLNAME, ContactSearch::EQ, "John Smith", isValid);
..and this: cs->AddStrTerm(Contact::P_SKYPENAME, ContactSearch::EQ, "john.smith", isValid); cs->AddOr(); cs->AddStrTerm(Contact::P_FULLNAME, ContactSearch::EQ, "John Smith", isValid);
..all search from both the P_FULLNAME and P_SKYPENAME fields.
Before using ContactGroup::Submit to start the search, you should always check whether the search criteria ended up being valid. This you can do with ContactSearch::IsValid method.
As you probably noticed, each of the AddXX methods also return a validity check boolean. However, it is a better practice to do the overall check as well, even if all the individual search criteria ended up looking Ok.
For example, lets take a search for contact's e-mail. This can be done with two different methods. Firstly we can use the ContactSearch::AddEmailTerm method. This method will actually validate whether the input is a valid e-mail address:
cs->AddEmailTerm ("test@test@test", isValid); will return the isValid argument as false.
However, you can also add the e-mail search criterion as a simple string, like this:
cs->AddStrTerm(Contact::P_EMAILS, ContactSearch::EQ, "test@test@test@", isValid); in which case the isValid will return true.
However, if you then check entire search object with:
cs->IsValid(isValid);
the isValid will correctly return false.
| Instance Methods | |||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
Inherited from Inherited from Inherited from |
|||
| Static Methods | |||
|
|||
|
Inherited from |
|||
| Class Variables | |
event_handlers =
|
|
propid2label =
|
|
module_id = 1
|
|
STATUS = Possible values for the ContactSearch.P_STATUS property. |
|
CONDITION = List of available matching conditions that can be used in AddTerm methods. |
|
P_CONTACT_SEARCH_STATUS = 200
|
|
|
Inherited from |
|
| Instance Variables | |
|
Inherited from |
| Properties | |
| contact_search_status | |
|
Inherited from |
|
| Method Details |
actual constructor
|
str(x)
|
construct CONTACT_BIRTHDAY term based on current time Arguments:
Return values:
|
construct CONTACT_BIRTHDAY term based on current time Arguments:
Return values:
|
Adds a search term against Contact::P_EMAILS property and pre-validates the value given in the email argument. Arguments:
Return values:
|
No description available. Arguments:
Return values:
|
Adds a string search term to a custom contact search object. Arguments:
|
Adds a search term to a custom contact search object. For now, there are only two searchable Contact properties that are integers, so this can oly be used for Contact::P_BIRTHDAY and Contact::P_GENDER. Arguments:
Return values:
|
checks that terms list is non-empty and does not contain unsupported keys Return values:
|
result list is dynamically updated Arguments:
Return values:
|
This callback is fired when a new matching contact has been found during the search. Return values:
|
| Class Variable Details |
STATUSPossible values for the ContactSearch.P_STATUS property.
|
CONDITIONList of available matching conditions that can be used in AddTerm methods.
|
| Property Details |
contact_search_status
|
| Home | Trees | Indices | Help |
|
|---|
| Generated by Epydoc 3.0.1 on Fri Mar 16 16:40:37 2012 | http://epydoc.sourceforge.net |