Bug 21296 - How should private tubes handle contact disconnection?
Summary: How should private tubes handle contact disconnection?
Status: NEW
Alias: None
Product: Telepathy
Classification: Unclassified
Component: gabble (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
: 25271 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-04-20 05:50 UTC by Guillaume Desmottes
Modified: 2009-11-25 02:15 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
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. ***


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.