[jbosscache-commits] JBoss Cache SVN: r7077 - core/trunk/src/main/docbook/userguide/en/modules.
jbosscache-commits at lists.jboss.org
jbosscache-commits at lists.jboss.org
Tue Nov 4 07:36:00 EST 2008
Author: manik.surtani at jboss.com
Date: 2008-11-04 07:35:59 -0500 (Tue, 04 Nov 2008)
New Revision: 7077
Modified:
core/trunk/src/main/docbook/userguide/en/modules/basic_api.xml
Log:
Explained node structure
Modified: core/trunk/src/main/docbook/userguide/en/modules/basic_api.xml
===================================================================
--- core/trunk/src/main/docbook/userguide/en/modules/basic_api.xml 2008-11-04 11:38:36 UTC (rev 7076)
+++ core/trunk/src/main/docbook/userguide/en/modules/basic_api.xml 2008-11-04 12:35:59 UTC (rev 7077)
@@ -152,6 +152,16 @@
assertFalse(cache.getRootNode().hasChild(peterGriffinFqn));
]]></programlisting>
+ <section>
+ <title>Organizing Your Data and Using the Node Structure</title>
+ <para>
+ A Node should be viewed as a named logical grouping of data. A node should be used to contain data for a
+ single data record, for example information about a particular person or account. It should be kept in
+ mind that all aspects of the cache - locking, cache loading, replication and eviction - happen on a per-node
+ basis. As such, anything grouped together by being stored in a single node will be treated as a single
+ atomic unit.
+ </para>
+ </section>
</section>
<section id="basic_api.fqn">
More information about the jbosscache-commits
mailing list