[
https://issues.apache.org/jira/browse/JENA-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962707#comment-14962707
]
ASF GitHub Bot commented on JENA-626:
-------------------------------------
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/pull/95#issuecomment-149066287
I'm a little confused by the fact that for a feature that seems to require
purchase only in an HTTP API (in Fuseki itself) this code seems to tangle all
the way down into very low-level serialization code and basic types. It seems
to me to be possible to do this reusing the extant caching machinery and doing
new work only in Fuseki. Perhaps you can explain a little about why you chose
to develop new caching machinery and why you integrated it in ARQ's
serialization machinery. Perhaps I am misunderstanding the intent here?
> SPARQL Query Caching
> --------------------
>
> Key: JENA-626
> URL: https://issues.apache.org/jira/browse/JENA-626
> Project: Apache Jena
> Issue Type: Improvement
> Reporter: Andy Seaborne
> Labels: java, linked_data, rdf, sparql
>
> Add a caching layer to Fuseki to cache the results of SPARQL Query requests.
> This cache should allow for in-memory and disk-based caching, configuration
> and cache management, and coordination with data modification.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
