Connection Pooling is a wayof handling connections to the database. The application server would create a set number of connections to the datasource (i,e the database) and would allow the users to use these connections within their code. Obtaining a connection to a DB is considered to be a costly operation and hence creating a pool at appserver startup is thought to overcome some of the performance problems.
Are there any good, free implementations around that can be recommended? The application would be client-side multi-threaded, so the one that comes with an application server is not what I'm looking for. Bart. [ September 12, 2003: Message edited by: Bart Sawyer ]
Bart.. I think some where in my code archive I have an implementation of the connection pool for Oracle. Not sure if that is what u are looking for... this was a pre-datasource in application servers think... if u need this I could zip it up.. i know at the time it was based on some freebie that was on the net.. i have lost info on where i got it from.. but I HAVE it...if u need this let me know..i would need an email to send it to
Hi, Essentially the term means your are creating a pool of connections. Getting connected to Database is an expensive deal from the resource n time consumed point of view. Thus we create typically a specific n - no of connections that would be established when the app. server is up. Cheers, Gaya3
I knew I would regret that burrito. But this tiny ad has never caused regrets: