I want to develop a java client side


program that will connect to a database (via jdbc).


The problem is that if i install jdbc


on the client i will have on the database


one connection per client, which i want to avoid.


I want the clients to share a maximum number


of physical connection on the database.


Here enters the connection pool.


How can use a connection pool in such an


architecture knowing that a Connection object


is not serialisable : i can't just send it to


client through a socket and wait untils it will


free it, right ?


The question is what do i put and use between the


database and the java remote clients.


Please don't answer me about tomcat and the jakarta-project (that i know)


because i need a pure big java swing pre-installed client (not an html/applet client).


Thanks a lot !
olivier