In order to efficiently use connection pooling via BoneCP while programming a Netty server- where is the correct place for the connection pool and where to get a new connection for that pool?
At a glance- I'm thinking that BoneCP should be some sort of global/singleton initialized just once in the main server, and then each handler (i.e. the class passed as "handler" to the pipeline) references that singleton to grab a new connection... but I don't see any examples of that on the net and, being new to Java, I'm a little concerned to jump right in with that approach. Would be great to hear an experienced voice!