You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by ji...@apache.org on 2004/10/23 21:51:37 UTC
[jira] Assigned: (DIRSEDA-13) Integration of ClientKey and ClientSession
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