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?
---
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.
---
