directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (DIRSEDA-10) UDP Imeplementation
Date Tue, 21 Sep 2004 15:10:47 GMT
The following comment has been added to this issue:

     Author: Alex Karasulu
    Created: Tue, 21 Sep 2004 8:10 AM
Good points! I knew we would hit a wall here since ClientKey is for state management and TCP
is stateful.  UDP is stateless so it was a matter of time.  Perhaps we should do an IRC session
and then come back and update this JIRA.  WDYT?  I'll be online tonight really late to talk.
View this comment:

View the issue:

Here is an overview of the issue:
        Key: DIRSEDA-10
    Summary: UDP Imeplementation
       Type: Task

     Status: Open
   Priority: Major

    Project: Seda Framework

   Assignee: Alex Karasulu
   Reporter: Trustin Lee

    Created: Mon, 20 Sep 2004 9:53 PM
    Updated: Tue, 21 Sep 2004 8:10 AM

SEDA framework currently supports TCP/IP only.  Supporting UDP is the primary concern to make
it widely usable.  But because of its essential difference with UDP, we have to approach carefully.

Datagram channels does not have notion of connect/disconnect.  DatagramChannel.validOps()
does not include OP_ACCEPT, so UDPListenerManager and UDPInputManager should be incorporated,
and it is slightly different from current routing process of SEDA.  This difference must be
handled smoothly to resolve this issue.

Because there is no explicit connection/disconnection notification, the policy how we should
maintin and expire ClientKeys.  Simplistic implementation will have an timeout-based expiration
mechanism.  As an alternative, SEDA can give up managing the sessions of UDP events although
I'm not sure it is possible.

Any ideas?

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