[VYSPER-292] Detecting unexpected network disconnects

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Component/s: connection handshake
• Assignee: Unassigned
• Reporter: Arun Prem
• Created: 08/Aug/11 06:09
• Updated: 17/Aug/11 09:17
• Resolved: 15/Aug/11 08:22

Description

This is similar to the one mentioned in the issue 286. Since there are no ways found to reopen the issue (which was already marked as 'Resolved'), I'm creating a new issue.

As a solution for the issue reported in 286, it is suggested to add a shutdown hook. But it seems it won't address the cases of unexpected network disconnects as given in the following scenario.

1. User1 logs in. The status is set as 'Available' by default.
==> User1's status is reflected in the messenger window of other logged in users.

2. Disconnect User1's workstation from the network.
==> Other user's list disappears from User1 messenger window.

3. Check the status of User1 from the messenger window of other logged in users.
==> User1's status still remains in the same for all other users.

Expected: User1's status should be made offline to other users as soon as the network disconnects.

The questions is how to detect the unexpected network disconnects for User1 and broadcast the status (as offline) to other logged-in users.

Thanks...

Issue Links

• is related to: VYSPER-286 Message cannot send message to offline receiver is not sent back to client