Rafal previously suggested the following, which I didn't do anything
with (yet):
One more random thought: maybe we could have
services.db.PoolBrokerService
instead services.db.DBBrokerService.
The old implementation util.db.pool.DBBroker should stay, the class
should
be marked as deprecated and become a wrapper for
services.db.TurbinePoolBroker and services.db.TurbineMapBroker
The DBBroker manages any number of connection pools, so this suggestion
actually makes a lot more sense to me. This will be backwards
compatible with the old setup (which is now deprecated). I was
wondering what everyone else's thoughts are on this?
--
Daniel Rall <[EMAIL PROTECTED]>
http://collab.net/ | open source | do the right thing
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
