directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Commented: (DIRSEDA-19) Does ListenerManager need to sub for DisconnectEvents?
Date Sun, 24 Oct 2004 04:04:26 GMT
The following comment has been added to this issue:

     Author: Trustin Lee
    Created: Sat, 23 Oct 2004 9:03 PM
       Body:
Is a SocketChannel is selected and does SocketChannel.read() returns -1 even if the other
thread explicitly closed it?  If so, we could remove this.
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/DIRSEDA-19?page=comments#action_54540

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/DIRSEDA-19

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 9:03 PM
    Due:     Fri, 20 Feb 2004 12:00 AM

Description:
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() ) ;
        
        try
        {
            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.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message