[Bug 53166] New: flawed representation of contact caps (can't deal with clients going away?)

[bugzilla-daemon at freedesktop.org]

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

             Bug #: 53166
           Summary: flawed representation of contact caps (can't deal with
                    clients going away?)
    Classification: Unclassified
           Product: Telepathy
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: salut
        AssignedTo: simon.mcvittie at collabora.co.uk
        ReportedBy: simon.mcvittie at collabora.co.uk
         QAContact: telepathy-bugs at lists.freedesktop.org


Gabble represents contact caps like this:

* Connection maintains a table { client name => caps set }
* When a new client appears, every channel manager is asked to
  "represent" that client, building up a list of caps that is the
  union of each channel manager's representation
* The caps emitted onto the network are the union of all clients'
  capabilities
* When a client goes away, it is removed from the table and the
  union is re-calculated

Salut, by contrast, does this:

* When a new client appears, every channel manager is asked to
  "represent" that client, storing the representation internally;
  it then emits the union of every client it cares about, including
  ones it isn't currently trying to represent

I'm not sure whether this deals correctly with clients going away.

It certainly requires more subtlety from channel managers than they ought to
have (see Ytstenut's plugin-base/caps-manager.c, and a Yts bug I'm about to
file).

Fixing this will break out-of-tree channel managers. The one in
ytstenut-plugins is the only known example.

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