🚀 go-pugleaf

"tom" <zhangx@gaia.ecs.csus.edu> wrote in message
news:431f62e7$1@newsgroups.borland.com...
>
> Is a standalone web start Java application a good candidate for connection
> pool?
>
>
>
The only benefit in this scenario, is to tier your application. Since each
client is creating its own connection (with a Client Application residing on
the user's desktop),
Connection Pooling only helps if you are obtaining and using connections
from a server pool.

The desktop would use the pool on the server. Make sure you get a handle to
the connection in your client app. If you do not, and you do not release the
connection back to the pool (ie. close the connection after each connection
is obtained), you are going to suffer from memory leaks.

However, the pool mechanism on the server, is only going to be a real
benefit from a stabd-alone app in getting connections faster and if you
remote some of your calls and make the client thinner anyway. If you are
planning to use the Database Components, it may not buy you much speed
improvement at all (unless you are planning some type of briefcase or rowset
type implementation).