Bug 24619

Summary: Satisfy disco waiters for a caps hash if we advertise that hash ourself
Product: Telepathy Reporter: Will Thompson <will>
Component: gabbleAssignee: Telepathy bugs list <telepathy-bugs>
Status: RESOLVED MOVED QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Will Thompson 2009-10-19 06:55:10 UTC 
Suppose we:

• sign in;
• get a hash "deadbeef" in a contact's presence, and disco it;
• get new capabilities set on us by MC, and our new hash turns out to be "deadbeef".

Now we should satisfy all the waiters for that hash immediately. Currently we do not.

Also, we should save contacts' hashes, so that if a disco request to them times out but actually comes back later, we can look up whose caps to update.
Comment 1 GitLab Migration User 2019-12-03 19:21:04 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/60.

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.