[Bug 24661] Undraft Connection.EnsureSidecar

[bugzilla-daemon at freedesktop.org]

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

--- Comment #12 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2010-09-29 04:59:46 PDT ---
(In reply to comment #11)
> - 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.

I changed the wording to be vague enough, and the API to be flexible enough,
that I think sidecars can use client interests fine.

> - 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).

I'd be happy to adjust the spec wording so it specifically allows this.

> - 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.

This is rather problematic in telepathy-glib, because TpContactFeature is an
enum rather than a (quark isomorphic to a) string, so there's no namespacing.
We could add an orthogonal TpContactExtendedFeature mechanism or something but
that's a bit full of bees.

When we break telepathy-glib ABI for spec 1.0 and/or GDBus, we should either
change TpContactFeature into a quark, or change both TpProxy and TpContact
features into an opaque pointer of some sort.

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