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/09/27 09:57:32 UTC

[jira] Created: (DIRSEDA-13) Integration of ClientKey and ClientSession

Message:

  A new issue has been created in JIRA.

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

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

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

[jira] Commented: (DIRSEDA-13) Integration of ClientKey and ClientSession

Posted by ji...@apache.org.
The following comment has been added to this issue:

     Author: Alex Karasulu
    Created: Mon, 27 Sep 2004 4:49 PM
       Body:
Looks interesting.  Does this address some of the inefficiency concerns you had with repeated key generation for UDP datagram handling?  It makes sense - I'd love to see more.  
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/DIRSEDA-13?page=comments#action_53451

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

    Created: Mon, 27 Sep 2004 12:55 AM
    Updated: Mon, 27 Sep 2004 4:49 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

[jira] Updated: (DIRSEDA-13) Integration of ClientKey and ClientSession

Posted by ji...@apache.org.
The following issue has been updated:

    Updater: Trustin Lee (mailto:trustin@gmail.com)
       Date: Sat, 23 Oct 2004 9:20 PM
    Changes:
             priority changed from Blocker to Minor
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/DIRSEDA-13?page=history

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

    Project: Seda Framework

   Assignee: Trustin Lee
   Reporter: Trustin Lee

    Created: Mon, 27 Sep 2004 12:55 AM
    Updated: Sat, 23 Oct 2004 9:20 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

[jira] Assigned: (DIRSEDA-13) Integration of ClientKey and ClientSession

Posted by ji...@apache.org.
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

[jira] Commented: (DIRSEDA-13) Integration of ClientKey and ClientSession

Posted by ji...@apache.org.
The following comment has been added to this issue:

     Author: Enrique Rodriguez
    Created: Mon, 27 Sep 2004 12:16 PM
       Body:
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:
  http://issues.apache.org/jira/browse/DIRSEDA-13?page=comments#action_53448

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

    Created: Mon, 27 Sep 2004 12:55 AM
    Updated: Mon, 27 Sep 2004 12:16 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