On 08/06/15 10:25, Claude Warren wrote:
What exactly is this review asking? Change in strategy or change in docs?
Both :-)
concurrency-howto does not mention transactions except in passing. It
shoudl be more pro-transactions IMO.
A possibility is that Dataset are all transactional, even is that is
only DatasetGraphWithLock;
No Dataset.supportsTransactions - its always true.
Remove Dataset.getlock.
concurrency-howto would be for model-only use. Everything else is
transaction in style. The documentation should reflect this preferred
style.
If we had (hi ajs6f!) an in-memory dataset as well as the general
container one, and the in-memory one were transactional, copy-in for
addGraph, we could make models be views of datasets always. Creating a
model would have an implicit Dataset if a free standing model.
Andy
On Fri, Jun 5, 2015 at 8:30 PM, Andy Seaborne (JIRA) <[email protected]>
wrote:
Andy Seaborne created JENA-957:
----------------------------------
Summary: Review concurrency howto in the light of
transactions.
Key: JENA-957
URL: https://issues.apache.org/jira/browse/JENA-957
Project: Apache Jena
Issue Type: Bug
Reporter: Andy Seaborne
Priority: Minor
http://jena.apache.org/documentation/notes/concurrency-howto.html
Include {{DatasetGraphWithLock}}.
Consider if that should be the default for in-memory and general datasets.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
