[jira] [Commented] (JENA-905) Common caching approach

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JENA-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504873#comment-14504873 ] 

ASF subversion and git services commented on JENA-905:
------------------------------------------------------

Commit 6e32ffc1e369ad45907f3d84f65ba7019e92cd35 in jena's branch refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=6e32ffc ]

Use Guava cache for LRU cache. Align atlas/lib/Cache interface.
JENA-801 JENA-905


> Common caching approach
> -----------------------
>
>                 Key: JENA-905
>                 URL: https://issues.apache.org/jira/browse/JENA-905
>             Project: Apache Jena
>          Issue Type: Improvement
>    Affects Versions: Jena 2.13.0
>            Reporter: Andy Seaborne
>            Assignee: Andy Seaborne
>
> Jena can consolidate around one caching implementation for several of these areas.
> Some uses of long term caches:
> * TDB (see JENA-801)
> * Rules (see JENA-901)
>  * ARQ
>    * DatasetGraphCaching, DatasetImpl
>     * org.apache.jena.riot.system.IRIResolver
> * Fuseki - SPARQL Query Caching (JENA-626)
> * Core - {{EnhGraph}}.
> One candidate is [Google Guava|https://github.com/google/guava]. It has the advantage of providing an atomic get-load operation that would be beneficial in some cases.
> However, many systems use different versions Guava. To stop Jena's choice of version clashing, we can shade a version to isolate it.
> [Email thread|http://mail-archives.apache.org/mod_mbox/jena-dev/201503.mbox/%3C550B094F.3020605%40apache.org%3E]
> [Pull request #45|https://github.com/apache/jena/pull/45]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)