[Bug 40933] Too many MembersChanged(Detailed) signals when connecting

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Sep 16 12:53:57 CEST 2011


Marco Barisione <marco.barisione at collabora.co.uk> changed:

           What    |Removed                     |Added
                URL|                            |http://cgit.collabora.com/g
                   |                            |it/user/bari/telepathy-glib
                   |                            |.git/log/?h=initial-members
                   |                            |-changed
             Status|NEW                         |ASSIGNED
           Keywords|                            |patch
         AssignedTo|telepathy-bugs at lists.freede |marco.barisione at collabora.c
                   |sktop.org                   |o.uk

--- Comment #1 from Marco Barisione <marco.barisione at collabora.co.uk> 2011-09-16 03:53:56 PDT ---
This branch fixes the problem by distinguishing when a contact appears in our
contact list because it's already there when we connect (so we group the
contacts and emit the signal with actor=0) and when contacts appear later
because they accepted our subscription request.

Another possible solution is to not emit the signal at all when connecting. I
looked into that, but I think that the fix looks more like a hack with little
gain (emitting one MembersChanged and one MembersChangedDetailed signal is not
a problem).

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.

More information about the telepathy-bugs mailing list