Hi all,

What do you think if we implement a simple, stupid path to Resource
cache in the ResourceResolver. This cache would be limited (LRUMap) with
a configurable size and be managed radically by completely clearing it
on each modification in the resource tree (e.g. upon a JCR Event).

The cache would be per-ResourceResolver, that is per-client-Request. For
this to not keep to much memory after the request, we need a lifecycle
management. This could be done by making use of the
JcrResourceResolverFactory.release(ResourceResolver) method.

The cache is solely present to be able to increase performance resolving
resources.

WDYT ?

Regards
Felix

Reply via email to