mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun Prem (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (VYSPER-292) Detecting unexpected network disconnects
Date Tue, 09 Aug 2011 09:48:27 GMT

     [ https://issues.apache.org/jira/browse/VYSPER-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Arun Prem updated VYSPER-292:

    Issue Type: Bug  (was: Sub-task)
        Parent:     (was: VYSPER-286)

> Detecting unexpected network disconnects
> ----------------------------------------
>                 Key: VYSPER-292
>                 URL: https://issues.apache.org/jira/browse/VYSPER-292
>             Project: VYSPER
>          Issue Type: Bug
>          Components: connection handshake
>            Reporter: Arun Prem
> 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
> The questions is how to detect the unexpected network disconnects for User1 and broadcast
the status (as offline) to other logged-in users.
> Thanks... 

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message