I was going through the SqlService source code and I observed the following thing: The SqlService maintains one connection per thread. So the number of active connections to the database is equal to the number of threads that have an instance of SqlService.
Given that, what is the best practice for maintaining a fixed sized connection pool? I attempted to follow slandao, but still not quite there yet.
brianWed 3 Nov 2010
Its actually an actor local, not a thread local which is subtly different. So a connection pool would be built using actors, although it would be very application specific.
rosarinjroy Wed 3 Nov 2010
I was going through the SqlService source code and I observed the following thing: The SqlService maintains one connection per thread. So the number of active connections to the database is equal to the number of threads that have an instance of SqlService.
Given that, what is the best practice for maintaining a fixed sized connection pool? I attempted to follow slandao, but still not quite there yet.
brian Wed 3 Nov 2010
Its actually an actor local, not a thread local which is subtly different. So a connection pool would be built using actors, although it would be very application specific.
go4 Mon 22 Nov 2010
@rosarinjroy FYR ConnectionPool