Return-Path: Delivered-To: apmail-incubator-geronimo-dev-archive@www.apache.org Received: (qmail 36677 invoked from network); 14 Oct 2003 19:44:55 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 14 Oct 2003 19:44:55 -0000 Received: (qmail 29854 invoked by uid 500); 14 Oct 2003 19:44:37 -0000 Delivered-To: apmail-incubator-geronimo-dev-archive@incubator.apache.org Received: (qmail 29797 invoked by uid 500); 14 Oct 2003 19:44:36 -0000 Mailing-List: contact geronimo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: geronimo-dev@incubator.apache.org Delivered-To: mailing list geronimo-dev@incubator.apache.org Received: (qmail 29784 invoked from network); 14 Oct 2003 19:44:36 -0000 Received: from unknown (HELO dns2.digitalglobe.com) (205.166.175.35) by daedalus.apache.org with SMTP; 14 Oct 2003 19:44:36 -0000 Received: from comail.digitalglobe.com (comail.digitalglobe.com [10.10.42.3]) by dns2.digitalglobe.com (8.11.6/8.11.6) with ESMTP id h9EDkXR23694 for ; Tue, 14 Oct 2003 20:46:33 +0700 Received: from pclnxbsnyder.digitalglobe.com ([10.10.30.169]) by comail.digitalglobe.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2656.59) id 46Y612LH; Tue, 14 Oct 2003 13:44:41 -0600 Date: Tue, 14 Oct 2003 19:44:41 +0000 (GMT) From: Bruce Snyder X-X-Sender: bsnyder@pclnxbsnyder.digitalglobe.com To: geronimo-dev@incubator.apache.org Subject: Re: Competing J2EE Connector implementation architectures In-Reply-To: <8D0003D0-FE77-11D7-9E60-003065F4889C@coredevelopers.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N This one time, at band camp, David Jencks said: DJ>Gianny Damour and I have developed alternate partial implementations of DJ>the JCA ConnectionManager. We haven't been able to convince each other DJ>of the merits of our own approach, so I think we need some broader DJ>community review and input. We also need an easier way to further DJ>develop our ideas in public. DJ> DJ>What I'd like to do is make 2 branches and check one proposal into DJ>each. I'd like some advice on what to call the branches. Here are a DJ>couple of ideas: DJ> DJ>1. Since Gianny's implementation calls most everything a Partition and DJ>mine calls most everything an Interceptor, DJ> DJ>J2EECA_PARTITION DJ> DJ>and DJ> DJ>J2EECA_INTERCEPTOR DJ> DJ>2. Use our initials... DJ> DJ>J2EECA_GD DJ> DJ>and DJ> DJ>J2EECA_DJ DJ> DJ>I'm also not sure if it's necessary to be politically correct and call DJ>it J2EECA rather than the usual and inaccurate JCA (== Java DJ>Cryptography Architecture). DJ> DJ>If there aren't any objections or better suggestions for names I'll use DJ>proposal (1). After checking in the code I'll explain more why I like DJ>my proposal better. Interesting that you're bringing this up, David. I was actually going to email you this week to find out your status and how your stuff differs from Gianny's. I think checking into two branches is a good idea. I like the following branch names: JCA_PARTITION JCA_INTERCEPTOR I also think that once this is checked in to CVS, only then can we proceed with a discussion on the mail list debating the merits of each one. If we're debating the two impls on the list without the code, it becomes tougher for everyone involved to truly understand what is being discussed. Bruce -- perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E