Julian Reschke created SLING-13307:
--------------------------------------
Summary: Resource Resolver: improve alias caching / handling
Key: SLING-13307
URL: https://issues.apache.org/jira/browse/SLING-13307
Project: Sling
Issue Type: Wish
Components: ResourceResolver
Reporter: Julian Reschke
Issues with Resource Resolver alias cache
- once initialized, the cache is treated as a complete view over all aliases
in the repo
- cache init can result in incorrect view due how JCR queries work (for
instance, incomplete or stale index, see
https://issues.apache.org/jira/browse/SLING-13284)
- Events received during cache init may be incomplete (best effort in JCR)
- not using the cache (Osgi config) isn't really an option due to slowness
(https://issues.apache.org/jira/browse/SLING-9535)
Why different from vanity paths?
- vanity path cache is (can be) size limited
- lookup of vanity paths "fast" anyway
Potential improvements:
- re-build the cache regularly, making it "eventually consistent"
- other ideas?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
