You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by oz...@apache.org on 2004/06/24 17:44:20 UTC
cvs commit: jakarta-commons-sandbox/transaction/xdocs/maps index.xml
ozeigermann 2004/06/24 08:44:20
Modified: transaction/xdocs/maps index.xml
Log:
Revision Changes Path
1.3 +12 -3 jakarta-commons-sandbox/transaction/xdocs/maps/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/jakarta-commons-sandbox/transaction/xdocs/maps/index.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- index.xml 24 Jun 2004 15:07:55 -0000 1.2
+++ index.xml 24 Jun 2004 15:44:20 -0000 1.3
@@ -16,7 +16,7 @@
commit the changes, i.e. make them permanent, or rather roll back the transaction by discarding all your changes.
</p>
-<p>As an example imagine a Swing client application where you do complex stuff (maybe
+<p>As an example imagine a client application where you do complex stuff (maybe
talking to one or more servers) and the user is allowed to cancel the
whole operation. Or it might be needed to be canceled because of errors that occur in the middle of the whole request.
Now image all the results have been stored in a transactional map and you
@@ -30,10 +30,19 @@
<a href="http://www.schemamania.org/jkl/booksonline/SQLBOL70/html/8_con_7a_1.htm">
most common concurrency problems</a> described in the scenario of authors working on documents.
Which phenomenon can occur with which map wrapper implementation can be found in
- <a href="wrappers-comparision.html">this chart</a>.
+ <a href="wrappers-comparision.html">this chart</a>.</p>
+<p>If none of
+the known phenomena is observable - which of course is the best you can get - a transaction is called <em>serializable</em>.
+ The origin of this term comes from a differet, but equivalent definition. This
+definition switches the perspective from local phenomena observed inside
+transactions to global one, more specific global corretctness. If a set of
+transactions are executed
+concurrently and there is a strictly sequential execution schedule of those transactions that leaves the
+map in the same state as the concurrent one those transactions are called <em>
+serializable</em>.
</p>
</section>
</body>
-</document>
\ No newline at end of file
+</document>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org