Bug 13597

Summary: Shouldn't decide whether contacts have PEP based on whether *we* do
Product: Telepathy Reporter: Simon McVittie <smcv>
Component: gabbleAssignee: Telepathy bugs list <telepathy-bugs>
Status: RESOLVED MOVED QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: minor    
Priority: low    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Simon McVittie 2007-12-10 11:43:19 UTC 
At the moment, at least some parts of Gabble decide whether to use PEP for a contact's properties based on whether we have PEP on our own server. This is clearly wrong.

The way to do this is probably to just try it, and if the error we get is service-not-implemented or something, cache that fact (perhaps in the presence cache) so we don't try it again. If I remember correctly, we do this (but without the caching) for PEP nicknames.

Alternatively, we could disco the contact's server and see if it has PEP, but that's probably a waste of round-trips.
Comment 1 GitLab Migration User 2019-12-03 19:17:21 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-gabble/issues/4.

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.