directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (DIRSEDA-13) Integration of ClientKey and ClientSession
Date Mon, 27 Sep 2004 19:17:33 GMT
The following comment has been added to this issue:

     Author: Enrique Rodriguez
    Created: Mon, 27 Sep 2004 12:16 PM
I see 'key' here and think encryption key, so I like the idea of phasing out ClientKey.  GNU-crypto,
BouncyCastle, and the Kerberos server code uses Key to mean encryption key.

View this comment:

View the issue:

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: Alex Karasulu
   Reporter: Trustin Lee

    Created: Mon, 27 Sep 2004 12:55 AM
    Updated: Mon, 27 Sep 2004 12:16 PM

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?

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