>From the db point of view opening a connection is resource(and time -) >consuming. So it's better to use a connectionpool. The "fetch from pool/push >back to pool" procs should be threadsafe. If you are unsure just write a >threadsafe wrapper around it.
@dom96 you could do that but it's a good idea to limit the amount of database connections. And you need a kind of "heartbeat" to check if the connection to the database is still alive. Normally that's handled by the connectionpool.
