From 5c196b3447dd24596c5591eb581412a3d8fb2566 Mon Sep 17 00:00:00 2001
From: Simon McVittie
The normalized contact's identifier. Not necessarily the same string
- as passed to
A list of strings indicating which D-Bus interfaces the calling + process is interested in. All supported attributes from these + interfaces, whose values can be obtained without additional network + activity, will be in the reply.
+ +Attributes from the interface
+
As well as returning cached information immediately, the
+ connection MAY start asynchronous requests to obtain better
+ values for the contact attributes. If better values are later
+ obtained by this process, they will be indicated with the usual
+ signals (such as
A dictionary mapping the contact handles to contact attributes. + If any of the requested handles are in fact invalid, they are + simply omitted from this mapping. If contact attributes are not + immediately known, the behaviour is defined by the interface; + the attribute should either be omitted from the result or + replaced with a default value.
+ +Each contact's attributes will always include at least the
+ identifier that would be obtained by inspecting the handle
+ (im.telepathy.v1.Connection/contact-id
).
A list of strings indicating which D-Bus interfaces the calling + process is interested in. All supported attributes from these + interfaces, whose values can be obtained without additional network + activity, will be in the reply.
+See
The contact's handle
+All supported attributes of the contact on + the given interfaces that can be returned without network + round-trips. If contact attributes are not immediately known, the + behaviour is defined by the interface; the attribute should either + be omitted from the result or replaced with a default value.
+ +The contact's attributes will always include at least the
+ identifier that would be obtained by inspecting the handle
+ (org.freedesktop.Telepathy.Connection/contact-id
).
This models a connection to a single user account on a communication service. Its basic capability is to provide the facility to request and @@ -747,6 +914,8 @@ USA.
and signals have been removed from this interface including anything to do with handle reference counting. +This interface deals with the multiple address types that can @@ -71,7 +70,7 @@
The behavior of this parameter is similar to the same
parameter in
-
The behavior of this parameter is similar to the same
parameter in
-
A list of strings indicating which D-Bus interfaces the calling
process is interested in. Equivalent to the corresponding argument
to A dictionary mapping the contact handles to contact attributes,
equivalent to the result of This library is free software; you can redistribute it and/or modify it
- under the terms of the GNU Lesser General Public License as published by
- the Free Software Foundation; either version 2.1 of the License, or (at
- your option) any later version. This library is distributed in the hope that it will be useful, but
- WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser
- General Public License for more details. You should have received a copy of the GNU Lesser General Public License
- along with this library; if not, write to the Free Software Foundation,
- Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. This interface allows many attributes of many contacts to be
- obtained in a single D-Bus round trip. Each contact attribute has an string identifier
- ( A list of strings indicating which D-Bus interfaces the calling
- process is interested in. All supported attributes from these
- interfaces, whose values can be obtained without additional network
- activity, will be in the reply. Attributes from the interface
- As well as returning cached information immediately, the
- connection MAY start asynchronous requests to obtain better
- values for the contact attributes. If better values are later
- obtained by this process, they will be indicated with the usual
- signals (such as A dictionary mapping the contact handles to contact attributes.
- If any of the requested handles are in fact invalid, they are
- simply omitted from this mapping. If contact attributes are not
- immediately known, the behaviour is defined by the interface;
- the attribute should either be omitted from the result or
- replaced with a default value. Each contact's attributes will always include at least the
- identifier that would be obtained by inspecting the handle
- ( A list of strings indicating which D-Bus interfaces the calling
- process is interested in. All supported attributes from these
- interfaces, whose values can be obtained without additional network
- activity, will be in the reply. See The contact's handle All supported attributes of the contact on
- the given interfaces that can be returned without network
- round-trips. If contact attributes are not immediately known, the
- behaviour is defined by the interface; the attribute should either
- be omitted from the result or replaced with a default value. The contact's attributes will always include at least the
- identifier that would be obtained by inspecting the handle
- (im.telepathy.v1.Connection/contact-id
).im.telepathy.v1.Connection/contact-id
).
When using this interface, it is a little like using the
-
Attempt to normalize the given contact ID. Where possible, this
SHOULD return the same thing that would be returned by