[jira] Closed: (DIRSEDA-10) UDP Imeplementation

[ji...@apache.org]

Message:

   The following issue has been closed.

   Resolver: Trustin Lee
       Date: Sat, 23 Oct 2004 8:59 PM

Implementation is basically done, I'll test this fixing DIRSEDA-4
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/DIRSEDA-10

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

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Seda Framework

   Assignee: Trustin Lee
   Reporter: Trustin Lee

    Created: Mon, 20 Sep 2004 9:53 PM
    Updated: Sat, 23 Oct 2004 8:59 PM

Description:
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?




---------------------------------------------------------------------
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