[Bug 21787] Connection.Interface.ContactLists

[bugzilla-daemon at freedesktop.org]

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

--- Comment #44 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2010-08-04 03:11:44 PDT ---
(I'd appreciate review on the spec changes for draft 3 - I think it's settled
down again, I have an implementation in Gabble, and David has reviewed the
corresponding telepathy-glib changes, so it'd be good to have the
telepathy-glib branch reflect the current draft in spec releases.)

In Bug #28200, David wonders whether some of the "plural" change methods should
instead only act on a single contact. If they're implemented as singular in
telepathy-glib, I think they should also be singular on D-Bus.

How does SIP/SIMPLE (where the contact list isn't stored by the server) look in
this API? Options are:

* UIs notice that SubscriptionsPersist is False but CanChangeSubscriptions is
True, and respond by storing the contact list locally (in libfolks?), and
dropping it into both AuthorizePublication and RequestSubscription every time
you connect.

* High-quality connection managers for SIMPLE are required to store your
contact list somewhere (~/.local/share/telepathy-sofiasip?) and have it take
effect every time you connect; SubscriptionsPersist is either removed, or kept
but marked as "for information only".

The spec currently says the former, but I think the latter may make more sense.

It's probably worth keeping SubscriptionsPersist for information - for
instance, the Maemo 5 UI currently says "Your contacts will be copied from the
server" if the protocol has ContactList channels, but if it was reimplemented
in terms of this API, it would only say that on protocols where
SubscriptionsPersist is True.

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