[Bug 21787] Connection.Interface.ContactLists

[bugzilla-daemon at freedesktop.org]

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

--- Comment #42 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2010-07-21 03:44:32 PDT ---
(In reply to comment #41)
> Another possibility is to have an Actor or Locally_Initiated or something in
> ContactsChanged.

I pressed [Commit] too soon... what I meant to say is "this is not at all
state-recoverable, but if we're discarding state-recoverability, then this
would be the way to do it".

Some other assorted thoughts based on the telepathy-glib implementation:

Splitting apart ContactsChanged and ContactsRemoved might make the API more
understandable. In all of telepathy-glib and Gabble, there's only one call to
tp_base_contact_list_contacts_changed where both parameters are non-NULL, and
in practice I don't think that will ever happen - the initial roster download
in Gabble we won't get removals, and in subsequent roster pushes, we only get
one item at a time.

TpBaseContactList has a virtual method that creates groups (necessary to
support CreateChannel/EnsureChannel for GROUP ContactList channels), but it
can't be invoked from the new API. Should it be added? My inclination would be
no: you can create a group as a side-effect, via AddToGroup("empty group", [])
or SetGroupMembers("empty group", []), if you really want to :-)

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