[Bug 50082] [next] Rely on contact attributes in all Connection ifaces

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=50082

--- Comment #4 from Jonny Lamb <jonny.lamb at collabora.co.uk> 2012-05-18 05:34:41 PDT ---
I think this is a good idea in principle.

(In reply to comment #1)
> """
> Also if there was no cached alias, a request
> SHOULD be started of which the result is later signalled by
> <tp:member-ref>AliasesChanged</tp:member-ref>."
> """

This feels like registering an interest in aliases and alias changes. Calling
GetAliases is an explicit "yeah, hit me" kind of thing. However, calling
GetContactAttributes on your contact list with Aliasing in the interface list
doesn't feel like the same thing to me, so I'm inclined to say the contact
attribute *shouldn't* make an alias request.

> GetLocation states almost the same, but GetClientTypes and GetContactInfo
> doesn't. Should we armonize this?

Same thing for Location.

Contact client types are discovered when you disco a contact, which you do
anyway, so that's not a problem. And do we get the contact's vcard anyway too?
I can't remember. 

But yes, it feels like 

> In XMPP, requesting the alias means fetching the vcard with avatar, right? Do
> we really want that?

Perhaps this answers my question. However if we're getting the vcard for
contact's contact info, then we also have the alias and avatar and...? but not
location.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.
You are the assignee for the bug.