[Bug 24661] Undraft Connection.EnsureSidecar

[bugzilla-daemon at freedesktop.org]

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

--- Comment #11 from Guillaume Desmottes <guillaume.desmottes at collabora.co.uk> 2010-07-15 05:15:00 PDT ---
I played a bit with sidecars recently and would like to discuss some points
regarding them.

- Currently once loaded side cars object stay alive during all the lifetime of
the connection right? Maybe we could do the same kind of magic than in the
client interest branch and destroy it once all the clients than ensured it are
gone?
This could be useful for example, if sidecars subscribes to some PEP ou pubsub
nodes to reduce XMPP traffic.

- Speaking of client interests. As I pointed on bug #27948, clients can't use
this API as sidecars's interface are not on the connection object; that could
be annoying. Note that if we destroy sidecars as I suggested above that could
be less of an issue.

- Same question regarding the Contacts interface. Could we imagine adding
attributes which are not interfaces on the Connection object? The spec doesn't
seem to say we can't and that should be easy to implement as the sidecar has
access to the connection object (it just have to call
tp_contacts_mixin_add_contact_attributes_iface on it).

- Assuming sidecars would be able to use the Contacts interface, it could be
handy for clients to be able to define their own contact features and hook it
to TpContact. So they'd just have to pass an extra feature to
tp_connection_get_contacts_by_handle() to magically get the extra data. That's
more a tp-glib issue than a spec one but I'm wondering how crack this idea is.

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