i think caching is up to the user, it needs to be configurable.
IMHO its better to have 2 separate projects, 1 Database Pool and the =
Other Database Caching.
WHY ? Because if someone implemented their own JDBC Connection Pool =
Manager, the only thing they want is a software to make some database =
("Resultset, x, y, z") caching and it would be helpful.
How ? We make it receive the resultsets you want to catch and set How =
many time you will have that result in memory, and other options.
This project is about tools not a full "Tool" to use just one feature.
I dont want to start a flame war ;)
Cheers,
Adrian
|
