----- Original Message ----- From: jon * <[EMAIL PROTECTED]> To: Turbine <[EMAIL PROTECTED]> Sent: Tuesday, December 28, 1999 3:48 PM Subject: Re: opl > on 12/28/99 12:37 PM, george stewart <[EMAIL PROTECTED]> wrote: > > > If someone is looking for something to contribute, > > they could submit an implementation of DbBroker which > > uses the one in turbine. Can this be done? > > > > I've been using Marc Mnich's from java exchange. I > > posted something to him about including it in opl but > > no answer. > > Yes, -1 on using the JavaExchange code. The reason why we did our own > connection pool is that I wanted something under a decent license and with > source code. Everything else out there either was not an acceptable license > to me (ie: GPL) or was like the JE stuff and didn't have source code. > > Also, it had to be singleton based. > > The Turbine, the connection pool follows all those requirements and works > quite well. It should be REALLY easy to use it with OPal. > > -jon > > -- > Come to the first official Apache Software Foundation > Conference! <http://ApacheCon.Com/> > > It is very easy... at one point i already had it in OPaL... could you give me a bit of time to review the code? you have made so many changes in the last three days i could not find the time to look at it in any detail. I plan to do this tonight. I will also piggyback on Turbine's DBBroker or maybe even remove opl/database/DbBroker and just use Turbine's DBBroker directly. i need to take a closer look at the code first though. as for JavaExchange code -1. one it is not needed and two i think that Turbine's DBBroker is just about as close to perfection as you can get for connection pooling with servlet based applications. -scott- ------------------------------------------------------------ To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Problems?: [EMAIL PROTECTED]
