Github user osma commented on the pull request:
https://github.com/apache/jena/pull/95#issuecomment-149196979
> Update operations must invalid the cache. A simple way is to simply
invalidate the whole cache. It is very hard to determine whether an update
affects a cache entry selectively.
This gives me an idea...
How about just adding support for a Last-Modified and/or ETag header to
Fuseki, based on the most recent update to the underlying data? Then any
compliant HTTP cache could be used in front of Fuseki. (There should also be a
Vary: Accept when that header was used to determine the result format.)
But if caching within Fuseki is truly needed, then I think Andy's detailed
review above charts the best ways of implementing it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
