Author: andy
Date: Wed Mar 28 21:48:12 2012
New Revision: 1306609
URL: http://svn.apache.org/viewvc?rev=1306609&view=rev
Log:
One dataset - one transaction
Modified:
incubator/jena/site/trunk/content/jena/documentation/tdb/tdb_transactions.mdtext
Modified:
incubator/jena/site/trunk/content/jena/documentation/tdb/tdb_transactions.mdtext
URL:
http://svn.apache.org/viewvc/incubator/jena/site/trunk/content/jena/documentation/tdb/tdb_transactions.mdtext?rev=1306609&r1=1306608&r2=1306609&view=diff
==============================================================================
---
incubator/jena/site/trunk/content/jena/documentation/tdb/tdb_transactions.mdtext
(original)
+++
incubator/jena/site/trunk/content/jena/documentation/tdb/tdb_transactions.mdtext
Wed Mar 28 21:48:12 2012
@@ -173,7 +173,7 @@ dataset.
## Multi-threaded use
-Each dataset object can have one transaction active at a time.
+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.
@@ -195,7 +195,7 @@ Thread 2:
} finally { dataset.end() ; }
Each thread has a separate `dataset` object; these safely share the
-same storage but each can have it's own transaction.
+same storage but have independent transaction.
While it is possible to shared a transaction between multiple
threads, this is not encouraged. Applications needing to do so must
