Disco request not invalidated when contact goes offline
Submitted by Alban Crequy
Assigned to Telepathy bugs list
Description
When a Gabble send a disco request to a contact, who goes offline meanwhile, the request is not invalidated.
Worse, if another contact has the same capability hash, he will not be sent a disco request: Gabble will wait the timeout before. And the timeout is incredibly long (20000 seconds).
We should:
- invalidate the request when the contact goes offline. smcv said the invalidation needs to be per-resource.
- reduce the timeout to a good value (20 seconds)
- add a unit test for the case contact goes offline and another contact has the same caps