Author: buildbot
Date: Wed Mar 28 17:22:41 2012
New Revision: 810437
Log:
Staging update by buildbot for jena
Modified:
websites/staging/jena/trunk/content/ (props changed)
websites/staging/jena/trunk/content/jena/documentation/tdb/tdb_transactions.html
Propchange: websites/staging/jena/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Mar 28 17:22:41 2012
@@ -1 +1 @@
-1306472
+1306478
Modified:
websites/staging/jena/trunk/content/jena/documentation/tdb/tdb_transactions.html
==============================================================================
---
websites/staging/jena/trunk/content/jena/documentation/tdb/tdb_transactions.html
(original)
+++
websites/staging/jena/trunk/content/jena/documentation/tdb/tdb_transactions.html
Wed Mar 28 17:22:41 2012
@@ -321,6 +321,12 @@ threads, this is not encouraged. Applica
ensure that within the transaction, all threads are acting
"multiple reader OR single writer". Change to the data within the
transaction must be executed one at a time.</p>
+<p>It is better not to share the same Dataset reference between different
+threads. Dataset objects are quite cheap to create via
+TDBFactory.create(location) and this ensure correct transaction
+handling. If, for some reason, in-memory TDB databases are needed,
+then the use of "named memory locations" is recommended: Location.mem("X").<br
/>
+</p>
<h2 id="multi-jvm">Multi JVM</h2>
<p>Multiple applications, running in multiple JVMs, using the same
file databases is not supported. There must be a single JVM
