[
https://issues.apache.org/jira/browse/JENA-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962919#comment-14962919
]
ASF GitHub Bot commented on JENA-626:
-------------------------------------
Github user osma commented on the pull request:
https://github.com/apache/jena/pull/95#issuecomment-149117326
Does this code notice when the underlying data is modified? E.g. if I do a
PUT between GET requests, is the cache invalidated? Not just after 5 minutes
but immediately.
For me this would the only good reason for having caching built in to Jena.
Otherwise an external HTTP cache such as Varnish would work just as well if not
better. See [this
example](https://github.com/NatLibFi/Skosmos/wiki/FusekiTuning#http-caching)
for how we use Varnish in front of Fuseki. It's very fast, the only problem is
that it's unaware of changes in the data and therefore must be manually
invalidated when the data is updated.
> 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)
