Return-Path: Delivered-To: apmail-incubator-directory-dev-archive@www.apache.org Received: (qmail 77972 invoked from network); 20 Sep 2004 16:33:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 20 Sep 2004 16:33:57 -0000 Received: (qmail 46902 invoked by uid 500); 20 Sep 2004 16:33:56 -0000 Delivered-To: apmail-incubator-directory-dev-archive@incubator.apache.org Received: (qmail 46846 invoked by uid 500); 20 Sep 2004 16:33:56 -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 46833 invoked by uid 99); 20 Sep 2004 16:33:56 -0000 X-ASF-Spam-Status: No, hits=0.6 required=10.0 tests=FROM_ENDS_IN_NUMS,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of aok123@bellsouth.net designates 205.152.59.66 as permitted sender) Received: from [205.152.59.66] (HELO imf18aec.mail.bellsouth.net) (205.152.59.66) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 20 Sep 2004 09:33:56 -0700 Received: from [172.16.1.8] ([65.80.200.112]) by imf18aec.mail.bellsouth.net (InterMail vM.5.01.06.11 201-253-122-130-111-20040605) with ESMTP id <20040920163352.VBYD1790.imf18aec.mail.bellsouth.net@[172.16.1.8]> for ; Mon, 20 Sep 2004 12:33:52 -0400 Subject: RE: [seda] API & IMPL project/jar consolidation From: Alex Karasulu To: Apache Directory Developers List In-Reply-To: <000501c49f2f$500b8cb0$1601a8c0@gloria> References: <000501c49f2f$500b8cb0$1601a8c0@gloria> Content-Type: text/plain Message-Id: <1095698219.8617.0.camel@fermi.trunk.joshua-tree.org> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Mon, 20 Sep 2004 12:36:59 -0400 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hey that actually sounds fair to me. What do others think? Alex On Mon, 2004-09-20 at 12:31, Stephen McConnell wrote: > > -----Original Message----- > > From: Alex Karasulu [mailto:aok123@bellsouth.net] > > Sent: 20 September 2004 17:56 > > To: Apache Directory Developers List > > Subject: RE: [seda] API & IMPL project/jar consolidation > > > > > > > > > (just > > > throw in a package protected console logger and you will eliminate > the > > > api pollution and close a security hole at the same time). > > > > So you mean make the monitors with deps on commons-logging package > > protected? > > No. > > Take commons-logging and make it disappear. Ok, so now you have done > this - you still have this pesky demo class that runs without a > container but you need to log stuff. So just throw together a console > logger of your own design - i.e. writes something dirty to System.out > inside a class called ConsoleMonitor or whatever. > > You end up delivering the demonstrable solution (that could be used in a > real scenario) but you are not opening up a security hole and will not > be introducing another "dirty api" (there are more than enough of them > out there already). > > Cheers, Steve. > > > >