directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Assigned: (DIRSEDA-13) Integration of ClientKey and ClientSession
Date Sat, 23 Oct 2004 19:51:37 GMT
Message:

   The following issue has been re-assigned.

   Assignee: Trustin Lee (mailto:trustin@gmail.com)
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/DIRSEDA-13

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: DIRSEDA-13
    Summary: Integration of ClientKey and ClientSession
       Type: Improvement

     Status: Open
   Priority: Blocker

    Project: Seda Framework

   Assignee: Trustin Lee
   Reporter: Trustin Lee

    Created: Mon, 27 Sep 2004 12:55 AM
    Updated: Sat, 23 Oct 2004 12:51 PM

Description:
Related issue: DIRSEDA-10

If I understood correctly, the relationship between 
ClientKey and ClientSession is 1:1, and both have the same meaning.  So why not merging them
into one class 'ClientSession' or 'Session'?

Here is my suggestion on interface hierarchy:

* Session
  * StatefulSession
  * StatelessSession
  * StreamIoSession

And here is the class hierarchy:

* AbstractSession implements Session
  * TcpSession implements StatefulSession, StreamIoSession
  * UdpSession implements StatelessSession, StreamIoSession
  * IntraVmSession implements StatefulSession

How is it?



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