[Telepathy] Proposed standard MC API

[Tobias Hunger]

On Thursday 02 August 2007, Alberto Mardegan wrote:
> ext George Wright wrote:
> >> Is Decibel using components only for handling channels as Nokia MC does,
> >> or do they something more?
> >
> > I believe they only handle channels. Decibel's components currently only
> > expose a channel handling API, but you'll have to talk to Tobias Hunger
> > about that.
>
> Nokia MC has also channel filters that can be installed as DBus
> components; it's something badly needed especially for handling incoming
> channels, so we should standardise that too.

What do those channel filters do?

> We need something more: a profile is an object having a display name, an
> icon, and a set of default protocol parameters. I think it's worth to
> create a DBus object for them, too.
> The account configuration clients will need to retrieve the list of
> available profiles (MC will take care of finding them in the filesystem
> and will provide a ListProfiles API), and present them (as a name and
> icon) to the user when he'll want to create a new account. Then, they
> will be used internally by MC to provide default values for the
> parameters that are unset in the account.
>
> IMHO, profiles (and protocols, and managers) should be considered
> read-only objects from a client point of view.

Why do you need to expose protocols and managers?

Best Regards,
Tobias
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.freedesktop.org/archives/telepathy/attachments/20070802/236cc335/attachment.pgp