Interface Channel.Addressing.DRAFT

Interface Index (Compact) | Summary | Description | Properties

Properties

TargetVCardField s Read only
TargetURIScheme s Read only
TargetVCardAddress s Read only
TargetURI s Read only
WARNING: This interface is experimental and is likely to cause havoc to your API/ABI if bindings are generated. Do not include this interface in libraries that care about compatibility.

Description

This interface provides properties that can be used fo requesting channels through different contact addressing schemes like vCard addresses or URIs.

Properties

Accessed using the org.freedesktop.DBus.Properties interface.
(Permalink)

TargetVCardField — s

Read only

The vCard field, normalized to lower case, TargetVCardAddress refers to.

The url vCard field MUST NOT appear here; see TargetURI instead.

Rationale:

In practice, protocols have a limited set of URI schemes that make sense to resolve as a contact.

If this is omitted from a request, TargetVCardAddress MUST be omitted as well.

(Permalink)

TargetURIScheme — s

Read only

The URI scheme used in TargetURI

Rationale:

While this seems redundant, since the scheme is included in TargetURI, it exists for constructing RequestableChannelClasses that support a limited set of URI schemes.

If this is omitted from a request, TargetURI MUST be omitted as well.

(Permalink)

TargetVCardAddress — s

Read only

The vCard address of the Channel's target.

If this is present in a channel request, TargetVCardField MUST be present, and TargetHandle, TargetID, and TargetURI MUST NOT be present. TargetHandleType must either not be present or set to Handle_Type_Contact. The request MUST fail with error InvalidHandle, without side-effects, if the requested vCard address cannot be found.

(Permalink)

TargetURI — s

Read only

The URI of the Channel's target. The URI's scheme (i.e. the part before the first colon) MUST be identical to TargetURIScheme.

If this is present in a channel request, TargetVCardField MUST be present, and TargetHandle, TargetID, and TargetVCardAddress MUST NOT be present. TargetHandleType must either not be present or set to Handle_Type_Contact. The request MUST fail with error InvalidHandle, without side-effects, if the requested vCard address cannot be found.