Consider a new object type for ConnectionManager to provide messaging API

[Kaffeine]

The idea is to keep Connection for connection API and use another object for everything else (that can be available without connection).

Draft

Description

The object holds the account context, so exposed properties nor methods don't have to specify the account for operation.

In order to allow AccountApi objects to be discovered by new clients, the object path and well-known bus name MUST be of the form /org/freedesktop/Telepathy/AccountApi/cmname/proto/account and org.freedesktop.Telepathy.AccountApi.cmname.proto.account where:

• cmname is the same Connection_Manager_Name that appears in the connection manager's object path and well-known bus name
• proto is the Protocol name as seen in ListProtocols, but with "-" replaced with "_" to get a valid object path/bus name
• account is some non-empty sequence of ASCII letters, digits, and underscores not starting with a digit

Types

Methods

Signals

Properties

Interfaces — DBus_Interface_List (Read only, Immutable)