Author: buildbot
Date: Tue Jul 22 10:12:24 2014
New Revision: 917079
Log:
Staging update by buildbot for jena
Modified:
websites/staging/jena/trunk/content/ (props changed)
websites/staging/jena/trunk/content/documentation/tdb/index.html
Propchange: websites/staging/jena/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Jul 22 10:12:24 2014
@@ -1 +1 @@
-1612393
+1612528
Modified: websites/staging/jena/trunk/content/documentation/tdb/index.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/tdb/index.html (original)
+++ websites/staging/jena/trunk/content/documentation/tdb/index.html Tue Jul 22
10:12:24 2014
@@ -155,10 +155,11 @@ otherwise noted.</p>
line scripts and via the Jena API. When accessed using <a
href="tdb_transactions.html">transactions</a>
a TDB dataset is protected against corruption, unexpected process terminations
and system crashes.</p>
<p>A TDB dataset <strong>should</strong> only be directly accessed from a
single JVM at a time otherwise data corruption
-may occur. If you wish to share a TDB dataset between multiple applications
please use our
+may occur. From 1.1.0 onwards TDB includes automatic protection against
multi-JVM usage which prevents this
+under most circumstances. If you wish to share a TDB dataset between multiple
applications please use our
<a href="../serving_data/">Fuseki</a> component which provides a SPARQL server
that
can use TDB for persistent storage and provides the SPARQL protocols
-for query, update and REST update over HTTP.</p>
+for query, update and REST update over HTTP. </p>
<h2 id="documentation">Documentation</h2>
<ul>
<li><a href="java_api.html">Using TDB from Java through the API</a></li>
