Return-Path: Delivered-To: apmail-commons-dev-archive@www.apache.org Received: (qmail 28904 invoked from network); 18 Oct 2010 15:40:00 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 18 Oct 2010 15:40:00 -0000 Received: (qmail 88350 invoked by uid 500); 18 Oct 2010 15:40:00 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 88250 invoked by uid 500); 18 Oct 2010 15:39:59 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 88242 invoked by uid 99); 18 Oct 2010 15:39:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Oct 2010 15:39:59 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of paulus.benedictus@gmail.com designates 209.85.210.43 as permitted sender) Received: from [209.85.210.43] (HELO mail-pz0-f43.google.com) (209.85.210.43) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Oct 2010 15:39:54 +0000 Received: by pzk9 with SMTP id 9so175184pzk.30 for ; Mon, 18 Oct 2010 08:39:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type:content-transfer-encoding; bh=J4qWPnso3XMBJytZ+hnCbO441Lnb6FCT2Q8rk8oGXAs=; b=CAarnx20GShLfrMCLtS9F9blQkO4vBmSbBefwyQDtHcsuIGUSl+m2YnfPPcyUobNLR wO33qDyLVk5EerhL61hSIRQI3JjQjcwq27XxPpdEg5hNSkANcxLF0XkuKiXV3lSIXdyi n/nUZm7/353MgjCcnVfJ7v41Ez+ZyhCIhaSeY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=E/jKBkNfhAlYUENGoyBEliZuyQwHSQ4W8VlpBaRVjJC3SOt7mynuN7s28j5aGpGftM P01B+ylwleGi0LKXGgsfDQWr2CMQ2Q6TT9YzOpLevHNa1L2gpOnrOAti8kD+7DI3tyir bbaDpPRGpUR2TMnUtZ7SbwJA/N+D1TpiSTciU= MIME-Version: 1.0 Received: by 10.142.213.16 with SMTP id l16mr3532847wfg.333.1287416373911; Mon, 18 Oct 2010 08:39:33 -0700 (PDT) Sender: paulus.benedictus@gmail.com Received: by 10.220.191.75 with HTTP; Mon, 18 Oct 2010 08:39:33 -0700 (PDT) In-Reply-To: References: <9CA3A0F6-75B2-46C1-9C4E-7DF5FF9FA150@seagullsoftware.com> <4CBB4AE8.90103@gmail.com> Date: Mon, 18 Oct 2010 10:39:33 -0500 X-Google-Sender-Auth: 1oVw6Ohq9mSBufULtxJmlFRAkhM Message-ID: Subject: Re: [pool][dbcp] cross pollination From: Paul Benedict To: Commons Developers List Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I didn't mean to imply one artifact with my suggestion. I would continue publishing two artifacts no matter what. On Mon, Oct 18, 2010 at 9:44 AM, Simone Tripodi wrote: > Hi all, > even if as developer was involved I recently, in therms of APIs, as > user, I'd prefeer keeping the 2 things separated: > > =A0* the pool is a set of APIs with interfaces and some concrete > implementations to create generic pools; i.e. I used it to pool > instances of commons-digester parsers or httpclient instances; > > =A0* the DBCP is a specific DatSource pool. > > I wouldn't like adding a generic pool library that brings the JDBC > connection pooling stuff, IMHO it continues making sense keeping the 2 > separated. > Just my 2 cents, > Simo > > http://people.apache.org/~simonetripodi/ > http://www.99soft.org/ > > > > On Mon, Oct 18, 2010 at 3:38 PM, Paul Benedict wro= te: >> Has any thought been given to simply rolling the projects into one? >> >> On Sun, Oct 17, 2010 at 2:13 PM, Phil Steitz wro= te: >>> On 10/17/10 2:58 PM, Gary Gregory wrote: >>>> >>>> Shouldnt we talk more across these two projects? Perhaps making sure w= e >>>> have good reuse and cross pollination >>> >>> Commons is *one* project. =A0That said, the answer is obviously yes. As= we >>> start to bring in the jdbc-pool stuff, this will become even more appar= ent. >>> =A0Coordination between [pool] and [dbcp] has never been an issue in th= e past >>> and I don't see that changing now. =A0Often fixing issues in [dbcp] end= s up >>> leading to [pool], so there has always been a lot of overlap in contrib= utors >>> to these two. >>> >>> Phil >>>> >>>> Gary >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org >>>> For additional commands, e-mail: dev-help@commons.apache.org >>>> >>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org >>> For additional commands, e-mail: dev-help@commons.apache.org >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org >> For additional commands, e-mail: dev-help@commons.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org > For additional commands, e-mail: dev-help@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org