Description

On some protocols it's possible to determine the type of client another
user is using, ranging from a simple "phone or not?" indicator to a
classification into several types of user interface. Telepathy represents
these using the client types defined by XMPP.

This section documents the auto-generated C wrappers for the
ClientTypes interface, used with TpConnection objects.

Return the client types of the given contacts, if they are already known. If any of the given contacts' client types are not known, request their current client types, but return immediately without waiting for a reply; if a reply with a non-empty client type array is later received for those contacts, the <tp:member-ref>ClientTypesUpdated</tp:member-ref> signal will be emitted for them. <tp:rationale> This method is appropriate for &quot;lazy&quot; client type finding, for instance displaying the client types (if available) of everyone in your contact list. </tp:rationale>

Return the current client types of the given contact. If necessary, make a request to the server for up-to-date information, and wait for a reply. <tp:rationale> This method is appropriate for use in a &quot;Contact Information...&quot; dialog; it can be used to show progress information (while waiting for the method to return), and can distinguish between various error conditions. </tp:rationale>

Signature of the callback called when a GetClientTypes method call
succeeds or fails.

proxy :

the proxy on which the call was made

out_Client_Types :

Used to return an 'out' argument if error is NULL: The contacts' client types, if already known. Contacts whose client types are not already known are omitted from the mapping; contacts known to have no client type information appear in the mapping with an empty list.