[jboss-cvs] JBossCache/docs/TreeCache/en/modules ...
Brian Stansberry
brian.stansberry at jboss.com
Mon Feb 12 11:07:58 EST 2007
User: bstansberry
Date: 07/02/12 11:07:58
Modified: docs/TreeCache/en/modules Tag: Branch_JBossCache_1_4_0
configuration.xml transactions.xml
Log:
[JBCACHE-976] Document that LockParentForChildInsertRemove default is false.
Revision Changes Path
No revision
No revision
1.10.2.7 +12 -0 JBossCache/docs/TreeCache/en/modules/Attic/configuration.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: configuration.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/docs/TreeCache/en/modules/Attic/configuration.xml,v
retrieving revision 1.10.2.6
retrieving revision 1.10.2.7
diff -u -b -r1.10.2.6 -r1.10.2.7
--- configuration.xml 30 Jan 2007 21:44:13 -0000 1.10.2.6
+++ configuration.xml 12 Feb 2007 16:07:58 -0000 1.10.2.7
@@ -379,6 +379,18 @@
<row>
<entry>
+ <para>LockParentForChildInsertRemove</para>
+ </entry>
+
+ <entry>
+ <para>Controls whether inserting or removing a node requires a write
+ lock on the node's parent (when pessimistic locking is used). The
+ default value is <code>false</code>.</para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
<para>MultiplexerService</para>
</entry>
1.2.4.3 +6 -6 JBossCache/docs/TreeCache/en/modules/Attic/transactions.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: transactions.xml
===================================================================
RCS file: /cvsroot/jboss/JBossCache/docs/TreeCache/en/modules/Attic/transactions.xml,v
retrieving revision 1.2.4.2
retrieving revision 1.2.4.3
diff -u -b -r1.2.4.2 -r1.2.4.3
--- transactions.xml 30 Jan 2007 03:20:16 -0000 1.2.4.2
+++ transactions.xml 12 Feb 2007 16:07:58 -0000 1.2.4.3
@@ -118,13 +118,13 @@
<para>
By default, before inserting a new node into the tree or removing an existing node from the
- tree, JBoss Cache will attempt to acquire a write lock on the new node's parent node. This
- approach treats child nodes as an integral part of a parent node's state. This approach
- provide greater correctness, but at a cost of lesser concurrency if nodes are frequently
- added or removed. For use cases where this greater correctness is not meaningful, JBoss
+ tree, JBoss Cache will only attempt to acquire a read lock on the new node's parent node.
+ This approach does not treat child nodes as an integral part of a parent node's state.
+ This approach allows greater concurrency if nodes are frequently added or removed, but
+ at a cost of lesser correctness. For use cases where greater correctness is necessary, JBoss
Cache provides a configuration option <literal>LockParentForChildInsertRemove</literal>.
- If this is set to <literal>false</literal>, insertions and removals of child nodes only
- require the acquisition of a <emphasis>read lock</emphasis> on the parent node.
+ If this is set to <literal>true</literal>, insertions and removals of child nodes
+ require the acquisition of a <emphasis>write lock</emphasis> on the parent node.
</para>
</section>
More information about the jboss-cvs-commits
mailing list