[Telepathy] Account and AccountManager objects

[Simon McVittie]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, 22 Jan 2008 at 20:04:52 +0200, mikhail.zabaluev at nokia.com wrote:
> >  AIUI the self-handle normalizes to sip:user at example.com too.
> >  (Mikhail, Senko: would a sip: URI be accepted as 'account'?)
> 
> Yes. Moreover, it's the preferred form, which will leave out any fuzzy heuristics.

I've wondered whether we should be heading towards more focus on URIs.
The proprietary protocols have such terrible URIs, though... they're all
verb-like rather than noun-like, and they're not something you want to
present in your UI.

> There's also a gorgeous idea to implement umbrella accounts, where one account in terms of UI would mean two or more connections managed by different CMs.

"gorgeous"? Sorry, I think you mis-spelled "terrifying" :-)

> The case in point is Gizmo XMPP/Sipphone SIP. Here, some form of a cascade connection manager would be necessary that presents a front end unifying disparate protocol connections and their handle namespaces.

The secondary connections would need some sort of magical hook to not
appear when browsing for connections, I think, to avoid your Gizmo
account looking like three connections (one umbrella account, one XMPP,
one SIP). Perhaps change the secondary connections' bus names to e.g.
org.freedesktop.Telepathy.SecondaryConnection.gabble.jabber.blahblah.

The handle validity situation seems likely to be frightening.

How does Gizmo cope if you add someone who only has XMPP with no
corresponding SIP? Or vice versa? Or does it just not support
syndication properly?

Anyway, I don't think this needs to be something we consider at the
moment.

    Simon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHlj0PWSc8zVUw7HYRAmYIAKDAxtyiokm2Zzex+QM0uC1r1W4dnACeJ4Nl
KGQW5DQYzPM4pSuxUL9yaTE=
=soW6
-----END PGP SIGNATURE-----