[Bug 21296] New: How private tubes should handle contact disconnection?

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Apr 20 14:50:28 CEST 2009


http://bugs.freedesktop.org/show_bug.cgi?id=21296

           Summary: How private tubes should handle contact disconnection?
           Product: Telepathy
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: telepathy-gabble
        AssignedTo: telepathy-bugs at lists.freedesktop.org
        ReportedBy: guillaume.desmottes at collabora.co.uk


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?


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the telepathy-bugs mailing list