Bug 16480 - ContactList: finally implement "stored" in CMs
Summary: ContactList: finally implement "stored" in CMs
Alias: None
Product: Telepathy
Classification: Unclassified
Component: tp-spec (show other bugs)
Version: unspecified
Hardware: Other All
: medium enhancement
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
Depends on: 19901 19902 19903
Blocks: tp-spec-1.0
  Show dependency treegraph
Reported: 2008-06-23 08:33 UTC by Alban Crequy
Modified: 2010-11-09 05:45 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Description Alban Crequy 2008-06-23 08:33:48 UTC
The spec defines the "publish" list and the "subscribe" list:

But we need a "known" list for contacts that the user has not subscribed to the presence nor sending its presence. This "known" list is already implemented in Gabble, but not specified. "known" is needed with Jabber because Telepathy clients cannot get all contacts from the Jabber roster otherwise.

I also would like Empathy to use this "known" list, see bug:
Comment 1 Simon McVittie 2009-02-02 03:55:40 UTC
Fixed in spec 0.17.14 with the "stored" list, but not widely (at all?) implemented.

For backwards compatibility, we should probably keep the misleadingly named "known" list on the CMs that already have it.
Comment 2 Mikhail Zabaluev 2009-12-30 05:10:08 UTC
Isn't this: 1) fixed; 2) going to be deprecated by bug #21787?
Comment 3 Will Thompson 2009-12-30 06:44:10 UTC
(In reply to comment #2)
> Isn't this: 1) fixed; 2) going to be deprecated by bug #21787?

Of the free CMs, I think only Gabble has stored.
Comment 4 Simon McVittie 2010-01-06 04:29:06 UTC
As you can see from "Depends On", there are still two CMs that lack 'stored' :-)

You're right that the new contact list API will deprecate all the ContactList channels, but that's no reason to not implement functionality that we already document.
Comment 5 Simon McVittie 2010-11-09 05:45:16 UTC
Won't fix, except by using TpBaseContactList.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.