Problems with NCO::IMAccount

[Daniele E. Domenichelli]

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

George Goldberg wrote:
> The correct solution to this problem is to support "capabilities" on
> an IMAccount, much like how Telepathy does it. "Audio" would be a
> capability, as would "Video" and other things (can't think of any
> examples off the top of my head, but there are plenty around).

I think that capabilities should also include file transfer, streams and
dbus tubes... probably all supported telepathy channel types [1] should
be listed here. User accounts capabilities should be filled querying
connection manager for Capabilities and buddies' IMAccounts using
ContactCapabilities. Also CapabilitiesChanged and
ContactCapabilitiesChanged signals should be listened and account
informations updated consequently.


That would be really useful, allowing for example to query nepomuk for:
IMAccounts that the "person me" has and that supports <X> and that
isBuddyOf an IMAccount that "Metacontact <Y>" has and that supports <X>,
where <X> can be audio, video, file transfer, tubes or even text (in
order to open a chat).

By the way, the previous query could theoretically return more than one
account. I think there should also be a field in telepathy ontology to
add a preference to an account (something like 0-5 stars for files).
This will allow to refine the query ordering by my accounts preference
and then by metacontact accounts preference and then just choose the
first result.



Daniele

[1] http://telepathy.freedesktop.org/spec/index.html#Channel-Types
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iJwEAQECAAYFAkvpdA4ACgkQLiFMXTq1e8s14gP/cdmCFxeAapAdfW23CohuyyTz
IcEa7InUOUeZJk/+cJRztYnyEsoflvGNvNr9b3pIIFZYD6pYraL4y97pPC5AIYEH
TqT1DzJeitkM52/ZRhbPLi4hFzfqXZfhowXinU2JFFJ2IvAijQVZx6KZ8sEXktOT
Zk46ZR6d55hL+JpwHfk=
=7/cS
-----END PGP SIGNATURE-----