Return-Path: Delivered-To: apmail-incubator-directory-dev-archive@www.apache.org Received: (qmail 83064 invoked from network); 27 Sep 2004 19:15:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 27 Sep 2004 19:15:44 -0000 Received: (qmail 80575 invoked by uid 500); 27 Sep 2004 19:15:43 -0000 Delivered-To: apmail-incubator-directory-dev-archive@incubator.apache.org Received: (qmail 80484 invoked by uid 500); 27 Sep 2004 19:15:42 -0000 Mailing-List: contact directory-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list directory-dev@incubator.apache.org Received: (qmail 80440 invoked by uid 99); 27 Sep 2004 19:15:42 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [192.18.33.10] (HELO exchange.sun.com) (192.18.33.10) by apache.org (qpsmtpd/0.28) with SMTP; Mon, 27 Sep 2004 12:15:40 -0700 Received: (qmail 29836 invoked from network); 27 Sep 2004 19:17:33 -0000 Received: from localhost (HELO nagoya) (127.0.0.1) by nagoya.betaversion.org with SMTP; 27 Sep 2004 19:17:33 -0000 Message-ID: <1404090455.1096312653759.JavaMail.apache@nagoya> Date: Mon, 27 Sep 2004 12:17:33 -0700 (PDT) From: jira@apache.org To: directory-dev@incubator.apache.org Subject: [jira] Commented: (DIRSEDA-13) Integration of ClientKey and ClientSession In-Reply-To: <866847863.1096271852427.JavaMail.apache@nagoya> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N 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