Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 4538 invoked from network); 15 Dec 2003 15:04:20 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 15 Dec 2003 15:04:20 -0000 Received: (qmail 49841 invoked by uid 500); 15 Dec 2003 15:04:13 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 49612 invoked by uid 500); 15 Dec 2003 15:04:12 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 49598 invoked from network); 15 Dec 2003 15:04:12 -0000 Received: from unknown (HELO exchange.sun.com) (192.18.33.10) by daedalus.apache.org with SMTP; 15 Dec 2003 15:04:12 -0000 Received: (qmail 8172 invoked by uid 50); 15 Dec 2003 15:04:28 -0000 Date: 15 Dec 2003 15:04:28 -0000 Message-ID: <20031215150428.8171.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: commons-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 25511] - allow for database clusters/clustering 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 DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25511 allow for database clusters/clustering ------- Additional Comments From hauser@acm.org 2003-12-15 15:04 ------- Below the answer of Dane (with his permission to distribute): ... The response to your question about an Apache style license is no. The BSD style license that the library is uses should be sufficiently flexible to allow the DBCP group to include the ideas and code that I have presented w/o modification to my existing license. If this is not the case please let me know where and how my license prevents this from happening and I will see what I can do to remedy it. The response to your suggestion to try to merge w/ DBCP is no. There are a couple of reasons for this: 1) I'm not very found of the Apache politics. To attempt to merge w/ DBCP means I would have to do things the Apache way and that is something I'm not even remotely interested in doing. 2) Though the end result of my initiative and the DBCP are the same. Our goals and process are sufficiently different to require pause. Apache: The DBCP is a general solution to the pooling problem. JDBC pooling is simply one of its manifestations. Dane: Cluster capable pooling is a specific problem that I'm trying to solve which happens to be a general solution to JDBC pooling. Apache: Reach the widest possible audience. Dane: Shun the spotlight. I don't view my work as an illustrious open source project w/ great ambitions and far reaching consequences. It's simply a solution to my problem that no one has solved thus far (AFAIK) and a problem that I assumed other people my be having. This is one of the reasons I've chosen a BSD style licenses. It allows people to take the idea and the rough sketch that is the code; and run w/ it as they see fit. The key thing for me is, there is a problem and I needed a solution, there was no readily available solution so I created one that suited my needs. If the code is good enough and the problem is one that enough people have, then making it available would have served its purpose. If that is not the case then the code has still served its purpose because it solved my problem. ... Dane. --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org