On 29/03/12 19:51, Bernie Greenberg wrote:
I have seemingly gotten this to work (but I said that last time, too) and
endure our fullest battery of tests, under the assumption of per-thread
"dataset"s, discarding them after a commit/end and creating a new one for
the thread when needed.
What the documentation needs, besides clear design guidelines for and a
minimal code example of multithreaded, transactional use, is a family of
diagrams explaining the scope, extent, uniqueness, and ownership of all the
kinds of data objects you can get (e.g., maps, datasets ...) with respect
to each other, databases, and threads.
Thanks again ----
Bernie
Hi Bernie,
There's a partial, quick change to the documention so it's at least been
vaguely helpful,
http://incubator.apache.org/jena/documentation/tdb/tdb_transactions.html#multi-threaded-use
Andy
