directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (DIRSEDA-8) ListenerConfig abstraction for TCP, UDP, and intra-VM pipes.
Date Sat, 18 Sep 2004 15:04:38 GMT
The following comment has been added to this issue:

     Author: Trustin Lee
    Created: Sat, 18 Sep 2004 8:04 AM
Here is an another patch which completes this issue:

- Renamed getURL() to getURI() to express a named pipe.
- Pushed down getInetServiceEntry() to SocketListenerConfig because PipeListenerConfig doesn't
seem to requite it.
- All ListenerConfigs does not depend on any ListenerAddresses; please see the patch file,
and you'll get to know they were not that useful.  It is safe to remove ListenerAddresses.
View this comment:

View the issue:

Here is an overview of the issue:
        Key: DIRSEDA-8
    Summary: ListenerConfig abstraction for TCP, UDP, and intra-VM pipes.
       Type: Improvement

     Status: In Progress
   Priority: Major

    Project: Seda Framework

   Assignee: Alex Karasulu
   Reporter: Trustin Lee

    Created: Thu, 16 Sep 2004 1:49 AM
    Updated: Sat, 18 Sep 2004 8:04 AM

ListenerConfig interface is currently specific to TCP transport, and we need to generalize
it and create subclasses we planned to support; SocketListenerConfig that covers TCP and UDP,
and PipeListenerConfig that covers intra-VM pipes.

Additionally, DefaultListenerManager is renamed to TCPListenerManager.

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