|
Hi there, First off, is anyone working on Connection pooling
(specifically JDBC connection pooling?) If not, I’d like to get
started working on that. Just to make sure that I’m on the right track, here’s
what I’m thinking: (sorry, copied from IRC chat…) I would just have to create a service, that on startup (depending to
the server config) creates connections to a JDBC client and keeps a few of those open, acting something like a FactoryObject
and parseling those out to apps that need them all the while keeping a minimum open to the JDBC datasource and possibly not letting them go too long. Also keeping in mind: *Connection Timeout / Testing *Security Management *Vendor Pools – is their API different? Or would this be a
configuration thing? TIA for your thoughts, -Matt |
- RE: Connections Pooling (JDBC) Matt Kurjanowicz
- RE: Connections Pooling (JDBC) gianny DAMOUR
- RE: Connections Pooling (JDBC) Matt Kurjanowicz
- RE: Connections Pooling (JDBC) gianny DAMOUR
- Re: Connections Pooling (JDBC) David Jencks
- Don't borrow from JBucks n. alex rupp
- Re: Don't borrow from JBucks David Jencks
