[Javtools-poolmngr] Caching resultsets

[Stefaan D. <st...@ya...>]

I have some serious thought about caching resultset. How large a cache of resultset
can be depends on the transactions which must be executed. If for example it is
usefull to cache 50 resultsets for one application and another demands about a 100
caching resultsets. These demands could go up very fast. 
The reason to point this out is that caching resultsets is only usefull in
situations where the retriction clause is not to restrictive (as pointed out by
Isabelle). 
This means that a resultset that could be cached would take alot of memory space on
a application server. 
As in accumulation of the above, there could be litterly put houndreds of resultsets
in the cache which leads to memory overloading of the server.

One possibility to this could be restricting the cache to a certain amount of memory
which seems very far fetched to me.

A pool manager should be capable of turning on any kind of machine powerfull or not.

Your opinion?

Stefaan
 

=====
Stefaan Delanghe
ICQ: 110055343

__________________________________________________
Do You Yahoo!?
Yahoo! Health - Feel better, live better
http://health.yahoo.com