Author: buildbot
Date: Wed Mar 28 21:48:23 2012
New Revision: 810460
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 21:48:23 2012
@@ -1 +1 @@
-1306608
+1306609
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 21:48:23 2012
@@ -314,7 +314,7 @@ dataset.</p>
<h2 id="multi-threaded-use">Multi-threaded use</h2>
-<p>Each dataset object can have one transaction active at a time.
+<p>Each dataset object has one transaction active at a time.
The usual idiom within multi-threaded applications is to have
one dataset per thread, and so there is one transaction per thread.</p>
<p>Thread 1:</p>
@@ -337,7 +337,7 @@ one dataset per thread, and so there is
<p>Each thread has a separate <code>dataset</code> object; these safely share
the
-same storage but each can have it's own transaction.</p>
+same storage but have independent transaction.</p>
<p>While it is possible to shared a transaction between multiple
threads, this is not encouraged. Applications needing to do so must
ensure that only one thread starts the transaction, via a <code>Dataset</code>
object,
