Interface Account.Interface.MinimumPresence.DRAFT2

Interface Index (Compact) | Summary | Description | Methods | Signals | Properties | Types

Methods

SetMinimumPresence ((uss): status) → nothing

Signals

MinimumPresenceRequestsChanged (a{s(uss)}: MinimumPresenceRequests)

Properties

MinimumPresenceRequests a{s(uss)} (Minimum_Presence_Request_Map) Read only

Types

Minimum_Presence_Request_Map Mapping a{s(uss)}
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.
Added in 0.19.12. (draft 2)
Objects implementing this interface must also implement:

Description

This interface extends the core Account interface to provide a way for applications to request minimum presence on the account.

Rationale:

Some applications, for example mail notifiers or address book synchronisation, can make use of account's connection even while the user is nominally offline.

Each client's unique name may set a minimum desired presence on the account. The combined presence is the most available presence of the minimum presences set and of RequestedPresence set by the user. The account manager should attempt to manipulate the connection to set the combined presence.

Methods

(Permalink)

SetMinimumPresence ((uss): status) → nothing

Parameters

Set a minimum presence needed by the client for this account. Setting (Offline, "offline", "") removes the minimum presence requirement for the client's unique name.

Signals

(Permalink)

MinimumPresenceRequestsChanged (a{s(uss)}: MinimumPresenceRequests)

Parameters

Emitted when the MinimumPresenceRequests property changes.

Properties

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

MinimumPresenceRequests — a{s(uss)} (Minimum_Presence_Request_Map)

Read only
Active requests for minimum presence status, a map of client unique name to the (non-offline) minimum presence they set.

Types

Mapping (Permalink)

Minimum_Presence_Request_Map — a{s(uss)}

A map of active minimum presence requests.

  • Key — s (DBus_Unique_Name)

    • Client unique name.

  • Value — (uss) (Simple_Presence)

    • Requested minimum presence.

    Rationale:

    Some applications may want to monitor the currently active minimum presences required. An example is an tool allowing the user to inspect applications maintaining open connections and close those applications.