Home · Modules · All Classes · All Namespaces
Public Slots | List of all members
Tp::Service::ConnectionInterfaceAddressingAdaptor Class Reference

#include <TelepathyQt/_gen/svc-connection.h>

Inheritance diagram for Tp::Service::ConnectionInterfaceAddressingAdaptor:
Inheritance graph
[legend]

Public Slots

Tp::AddressingNormalizationMap GetContactsByVCardField (const QString &field, const QStringList &addresses, const QStringList &interfaces, const QDBusMessage &dbusMessage, Tp::ContactAttributesMap &attributes)
 
Tp::AddressingNormalizationMap GetContactsByURI (const QStringList &URIs, const QStringList &interfaces, const QDBusMessage &dbusMessage, Tp::ContactAttributesMap &attributes)
 

Additional Inherited Members

- Public Member Functions inherited from Tp::AbstractAdaptor
 AbstractAdaptor (const QDBusConnection &connection, QObject *adaptee, QObject *parent)
 
 ~AbstractAdaptor ()
 
QDBusConnection dbusConnection () const
 
QObject * adaptee () const
 

Detailed Description

Adaptor class providing a 1:1 mapping of the D-Bus interface "org.freedesktop.Telepathy.Connection.Interface.Addressing1".

Member Function Documentation

◆ GetContactsByVCardField

Tp::AddressingNormalizationMap Tp::Service::ConnectionInterfaceAddressingAdaptor::GetContactsByVCardField ( const QString &  field,
const QStringList &  addresses,
const QStringList &  interfaces,
const QDBusMessage &  dbusMessage,
Tp::ContactAttributesMap attributes 
)
slot

Begins a call to the exported D-Bus method GetContactsByVCardField on this object.

Adaptees should export this method as a Qt slot with the following signature: void getContactsByVCardField(const QString& field, const QStringList& addresses, const QStringList& interfaces, const Tp::Service::ConnectionInterfaceAddressingAdaptor::GetContactsByVCardFieldContextPtr &context);

Implementations should call MethodInvocationContext::setFinished (or setFinishedWithError accordingly) on the received context object once the method has finished processing.

Request contacts and retrieve their attributes using a given field in their vCards.

The connection manager should record that these handles are in use by the client who invokes this method, and must not deallocate the handles until the client disconnects from the bus or calls the ConnectionInterface::ReleaseHandles() method.

Parameters
field
\htmlonly
<p>The vCard field of the addresses we are requesting. The
  field name SHOULD be in lower case. Supported
  fields can be found in
   \\\\endhtmlonly \\\\link ProtocolInterfaceAddressingInterface::requestPropertyAddressableVCardFields() ProtocolInterfaceAddressingInterface::AddressableVCardFields \\\\endlink \\\\htmlonly .</p>

<p>The <code>url</code> vCard field MUST NOT appear here; see
   \\\\endhtmlonly GetContactsByURI() \\\\htmlonly  instead.</p>

<div class="rationale">
  <p>In practice, protocols have a limited set of URI
    schemes that make sense to resolve as a contact.</p>
</div>
\endhtmlonly
addresses
The addresses to get contact handles for. The address types should 
match the given vCard field.
interfaces
\htmlonly
<p>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.</p>

<p>Attributes from this interface and from
   \\\\endhtmlonly ConnectionInterface \\\\htmlonly 
  are always returned, and need not be requested
  explicitly.</p>

<p>The behavior of this parameter is similar to the same
  parameter in
   \\\\endhtmlonly ConnectionInterfaceContactsInterface::GetContactAttributes() \\\\htmlonly .</p>
\endhtmlonly
attributesOutput parameter
\htmlonly
<p>A dictionary mapping the contact handles to contact attributes.
  If any of the requested addresses 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.</p>

<p>Requested addresses that are not valid or understood for this protocol
  MUST be omitted from the mapping.</p>

<p>Each contact's attributes will always include at least the
  identifier that would be obtained by inspecting the handle
  (<code>org.freedesktop.Telepathy.Connection/contact-id</code>).
</p>
\endhtmlonly
Returns
\htmlonly
<p>A mapping from requested vCard addresses to the corresponding
  contact handles.</p>

<p>Requested addresses that are not valid or understood for this protocol
  MUST be omitted from the mapping.</p>
\endhtmlonly

◆ GetContactsByURI

Tp::AddressingNormalizationMap Tp::Service::ConnectionInterfaceAddressingAdaptor::GetContactsByURI ( const QStringList &  URIs,
const QStringList &  interfaces,
const QDBusMessage &  dbusMessage,
Tp::ContactAttributesMap attributes 
)
slot

Begins a call to the exported D-Bus method GetContactsByURI on this object.

Adaptees should export this method as a Qt slot with the following signature: void getContactsByURI(const QStringList& URIs, const QStringList& interfaces, const Tp::Service::ConnectionInterfaceAddressingAdaptor::GetContactsByURIContextPtr &context);

Implementations should call MethodInvocationContext::setFinished (or setFinishedWithError accordingly) on the received context object once the method has finished processing.

Request contacts and retrieve their attributes using URI addresses.

The connection manager should record that these handles are in use by the client who invokes this method, and must not deallocate the handles until the client disconnects from the bus or calls the ConnectionInterface::ReleaseHandles() method.

Parameters
URIs
The URI addresses to get contact handles for. Supported schemes can 
be found in AddressableURISchemes.
interfaces
\htmlonly
<p>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.</p>

<p>Attributes from this interface and from
   \\\\endhtmlonly ConnectionInterface \\\\htmlonly 
  are always returned, and need not be requested
  explicitly.</p>

<p>The behavior of this parameter is similar to the same
  parameter in
   \\\\endhtmlonly ConnectionInterfaceContactsInterface::GetContactAttributes() \\\\htmlonly .</p>
\endhtmlonly
attributesOutput parameter
\htmlonly
<p>A dictionary mapping the contact handles to contact attributes.
  If any of the requested addresses 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.</p>

<p>Requested URIs that are not valid or understood for this protocol
  MUST be omitted from the mapping.</p>

<p>Each contact's attributes will always include at least the
  identifier that would be obtained by inspecting the handle
  (<code>org.freedesktop.Telepathy.Connection/contact-id</code>).
</p>
\endhtmlonly
Returns
\htmlonly
<p>A mapping of requested URIs to the corresponding contact handles.</p>

<p>Requested URIs that are not valid or understood for this protocol
  MUST be omitted from the mapping.</p>
\endhtmlonly