[
https://issues.apache.org/jira/browse/MARMOTTA-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562786#comment-13562786
]
Sebastian Schaffert commented on MARMOTTA-38:
---------------------------------------------
The new implementation is agnostic to the way the backend is caching the
triples. It just expects a RepositoryConnection and updates the triples with
the cached subject resource there (i.e. removes old triples and adds new
triples).
In case you want to store the triples in the same repository as your local
triples (like in the LMF), my current plan is to use a Sesame
ContextAwareConnection for caching:
http://www.openrdf.org/doc/sesame2/2.7.0-beta1/api/org/openrdf/repository/contextaware/ContextAwareConnection.html
In this way you can specify the context to use at a pretty high level in the
architecture.
> Named chaches
> -------------
>
> Key: MARMOTTA-38
> URL: https://issues.apache.org/jira/browse/MARMOTTA-38
> Project: Marmotta
> Issue Type: Improvement
> Components: Libraries
> Affects Versions: 2.6
> Environment: ldcache
> Reporter: Sergio Fernández
> Assignee: Sebastian Schaffert
> Priority: Minor
>
> Now that LDCache is being refactorized, maybe we could try to allow cache the
> data in different named graphs. By default the current mechanism is fine, but
> in some scenario it could be useful to have the data clearly separated, not
> sure if optional named graphs per provider or explicit named graph selection.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
