Bug 29421

Summary:	Channel-specific handle API is lacking
Product:	Telepathy	Reporter:	Olli Salli <ollisal>
Component:	tp-qt	Assignee:	Telepathy bugs list <telepathy-bugs>
Status:	RESOLVED MOVED	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	enhancement
Priority:	low
Version:	git master
Hardware:	All
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Olli Salli 2010-08-06 09:22:49 UTC

TpQt4 Channel objects currently go to great lengths to ensure an application doesn't have to build Contact objects for the members of the channel by itself. This breaks, however, if channel-specific handles are in use (used in eg. XMPP multi-user chats, where users have nicknames, not always directly exposing their global JID). Currently, only a best-effort local handle -> global handle map is provided.

API should be added to provide a local contact pointer (weakref?) to a global contact pointer mapping. Maintaining this mapping requires additional D-Bus roundtrips to construct the global contacts, so it should be an optionally requested Feature.

If feasible, API should be added to Tp::Contact to tell if it's a channel-specific contact, and to access the corresponding global contact, if any. This needs synchronizing the handle owner contact object construction and group change contact object construction and making the association there, though.

Comment 1 GitLab Migration User 2019-12-03 20:27:18 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-qt/issues/7.

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.