directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Assigned: (DIRSEDA-19) Does ListenerManager need to sub for DisconnectEvents?
Date Sat, 23 Oct 2004 19:51:32 GMT

   The following issue has been re-assigned.

   Assignee: Trustin Lee (
View the issue:

Here is an overview of the issue:
        Key: DIRSEDA-19
    Summary: Does ListenerManager need to sub for DisconnectEvents?
       Type: Task

     Status: Open
   Priority: Minor

    Project: Seda Framework

   Assignee: Trustin Lee
   Reporter: Alex Karasulu

    Created: Fri, 20 Feb 2004 12:28 AM
    Updated: Sat, 23 Oct 2004 12:50 PM
    Due:     Fri, 20 Feb 2004 12:00 AM

Looks like the ListenerManager is stuck with the odd job of 
handing disconnects:

    public void inform( DisconnectEvent an_event )
        m_clients.remove( an_event.getClientKey() ) ;
            an_event.getClientKey().expire() ;
        catch ( IOException e ) 
            m_monitor.failedToExpire( an_event.getClientKey(), e ) ;

Do we need this here? The clients are kept here in the DefaultListenerManager but is that
the right place for them?  This should be checked out.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message