[
https://issues.apache.org/jira/browse/OAK-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Mueller updated OAK-3583:
--------------------------------
Description:
The currently used Guava Cache API should not be used, so that we no longer
depend on Guava.
The JCache API [1] could be used maybe. The JCache API implementation should be
configurable/ pluggable so it could support one of the available distributed
implementations [2].
[1] https://jcp.org/en/jsr/detail?id=107
[2] https://jcp.org/aboutJava/communityprocess/implementations/jsr107/index.html
was:
The JCache API [1] was finally released and is ready to be used.
Ideally the currently used Guava Cache is replaced by the JCache API. The
JCache API implementation should be configurable/ pluggable so it could support
one of the available distributed implementations [2].
The default should be a wrapper around the current Guava Cache and LIRSCache
implementations.
[1] https://jcp.org/en/jsr/detail?id=107
[2] https://jcp.org/aboutJava/communityprocess/implementations/jsr107/index.html
> Replace Guava API for caching
> -----------------------------
>
> Key: OAK-3583
> URL: https://issues.apache.org/jira/browse/OAK-3583
> Project: Jackrabbit Oak
> Issue Type: Wish
> Components: cache
> Reporter: Philipp Suter
> Priority: Major
>
> The currently used Guava Cache API should not be used, so that we no longer
> depend on Guava.
> The JCache API [1] could be used maybe. The JCache API implementation should
> be configurable/ pluggable so it could support one of the available
> distributed implementations [2].
> [1] https://jcp.org/en/jsr/detail?id=107
> [2]
> https://jcp.org/aboutJava/communityprocess/implementations/jsr107/index.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
