Bug 21296

Summary: How should private tubes handle contact disconnection?
Product: Telepathy Reporter: Guillaume Desmottes <guillaume.desmottes>
Component: gabbleAssignee: Telepathy bugs list <telepathy-bugs>
Status: RESOLVED MOVED QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: normal    
Priority: medium CC: cmaiku
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Guillaume Desmottes 2009-04-20 05:50:28 UTC 
It's not clear how Gabble should manage the following scenario:
- Alice offers a tube to Bob
- Bob disconnects without properly close the tube

It would be good for Gabble to close it to avoid to let old tubes alive during the whole lifetime of the connection. But closing tubes when contact disconnects will break tubes if the contact was actually setting his presence to invisible.

Should we start to ping the contact when he appears to be offline?
Should we rely on the bytestream connectivity checks?
Should we distinguish offered and not offered yet tube channels?
Comment 1 Guillaume Desmottes 2009-04-20 05:52:03 UTC 
This branch close the tube when contact appears to be offline:
http://git.collabora.co.uk/?p=user/cassidy/telepathy-gabble;a=shortlog;h=refs/heads/tube-closed
Comment 2 Guillaume Desmottes 2009-11-25 02:15:51 UTC 
*** Bug 25271 has been marked as a duplicate of this bug. ***
Comment 3 GitLab Migration User 2019-12-03 19:19:01 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/28.

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.