[Telepathy] TransportHander API proposal

Simon McVittie simon.mcvittie at collabora.co.uk
Tue Apr 15 04:55:29 PDT 2008

Hash: SHA1

On Tue, 15 Apr 2008 at 14:35:56 +0300, mikhail.zabaluev at nokia.com wrote:
> I agree that most of it is too complicated and we are not going to need it (and when we do, the requirements will be different enough to warrant a redesign anyway). See YAGNI principle.


> I'd retain Conditions, though
> I think the Plugin property in that interface is unnecessary, as it serves a special case of binding to one plugin. That can be done using conditions alone.

Yes, if an account particularly wants a plugin-specific condition to be
true, it can ask for it. {"x-maemo-bluetooth-enabled": "1"} might be a
condition that's only ever satisfied by the Maemo bluetooth connectivity

I'm not quite sure why the values in Mardy's Conditions draft are
strings rather than variants (in practice I expect a lot of conditions
are going to be boolean) but if we introduce a convention that boolean
conditions always have value "0" or "1" it should be OK.

I think a reasonably well thought-out list of well-known keys is needed.

Mardy's draft doesn't cover all the use cases mentioned in the
rationale (negating rules to have an account which is connected when not
at work), which is amusing... perhaps someone can think of a more elegant way
to achieve the same result?



More information about the Telepathy mailing list