[
https://issues.apache.org/jira/browse/JENA-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15833716#comment-15833716
]
ASF GitHub Bot commented on JENA-1274:
--------------------------------------
Github user ajs6f commented on the issue:
https://github.com/apache/jena/pull/204
I'm starting to wonder whether I should back up here and just go for the
more general 2-phase-locking design as [@afs discusses in the Jira
ticket](https://issues.apache.org/jira/browse/JENA-1274?focusedCommentId=15809288&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15809288),
or even to try to generalize to more amorphous locking regions. Doing those
things would open up more use cases which might make this stuff viable for
`jena-arq` itself.
> Support a writer-per-graph in-memory dataset
> --------------------------------------------
>
> Key: JENA-1274
> URL: https://issues.apache.org/jira/browse/JENA-1274
> Project: Apache Jena
> Issue Type: Improvement
> Components: ARQ, Jena
> Reporter: A. Soroka
> Assignee: A. Soroka
> Priority: Minor
> Labels: ldp, multithreading, named_graphs
>
> Without too much work we could support a writer-per-graph in-memory dataset.
> The target use case here is LDP-style interaction or other RESTful
> architectures, where it is normal for updates to occur centered on one
> resource.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
