get_contact_attributes

Description:

[ Version ( deprecated = true ) ]
public void get_contact_attributes (int timeout_ms, Handle[] handles, string interfaces, bool hold, owned Callback callback, Object weak_object)

Warning: get_contact_attributes is deprecated.

Return (via a callback) any number of attributes of the given handles.

Note:

Use ensure_contact instead.

Since telepathy-glib version 0.13.8, the handles will remain valid until connection becomes invalid (signalled by invalidated). In earlier versions, if hold was true, the callback would hold a reference to them which could be released with unref_handles.

This is a thin wrapper around the GetContactAttributes D-Bus method, and should be used in preference to tp_cli_connection_interface_contacts_call_get_contact_attributes; mixing this function, hold_handles, unref_handles, and Contact with direct use of the RequestHandles, HoldHandles and GetContactAttributes D-Bus methods is unwise, as Connection and Contact perform client-side reference counting of handles. The Contact API provides a higher-level abstraction which should usually be used instead.

callback will later be called with the attributes of those of the given handles that were valid. Invalid handles are simply omitted from the parameter to the callback.

If hold is true, the callback is given one reference to each handle that appears as a key in the callback's attributes parameter.

Parameters:

this	a connection
timeout_ms	the timeout in milliseconds, or -1 to use the default
handles	an array of handles
interfaces	a `GStrv` of interfaces
hold	if `true`, the callback will hold one reference to each valid handle
callback	called on success or failure (unless `weak_object` has become unreferenced)
weak_object	if not `null`, an object to be weakly referenced: if it is destroyed, `callback` will not be called
destroy	called to destroy `user_data` after calling `callback`, or when `weak_object` becomes unreferenced (whichever occurs sooner)
n_handles	the number of handles in `handles` (must be at least 1)
user_data	arbitrary user-supplied data