Hi, > I think there could be a couple of metrics for limiting the cache size: > maximum elements, or maximum size (which would require keeping track of > object sizes, which could be tricky). And both of these would probably > require an LRU list for throwing out the ones that aren't being used > frequently (which isn't in there at the moment either). Ok, I agree completely. Maybe for 2.1 we could think on a pluggable cache implementation to be put in applicationcontext, and keep the existing one as the only implementation in Pivot, what do you think ?
> Some documentation would definitely help to understand the issues. I'd put some comment in Javadoc in the meantime, for 2.0.3 ... Bye
