[jboss-cvs] JBossAS SVN: r82258 - projects/docs/community/5/Clustering_Guide/en-US.

[jboss-cvs-commits at lists.jboss.org]

Author: bstansberry at jboss.com
Date: 2008-12-13 10:38:29 -0500 (Sat, 13 Dec 2008)
New Revision: 82258

Modified:
   projects/docs/community/5/Clustering_Guide/en-US/Clustering_Guide_Introduction.xml
Log:
Fix TOC hierarchy

Modified: projects/docs/community/5/Clustering_Guide/en-US/Clustering_Guide_Introduction.xml
===================================================================
--- projects/docs/community/5/Clustering_Guide/en-US/Clustering_Guide_Introduction.xml	2008-12-13 15:11:55 UTC (rev 82257)
+++ projects/docs/community/5/Clustering_Guide/en-US/Clustering_Guide_Introduction.xml	2008-12-13 15:38:29 UTC (rev 82258)
@@ -122,16 +122,18 @@
 	</note>
 
 </section>
+
 <section><title>JBoss Cache channels</title>
 <para>
 	JBoss Cache is a fully featured distributed cache framework that can be used in any application server environment or standalone. JBoss AS integrates JBoss Cache to provide cache services for HTTP sessions, EJB 3.0 session beans, and EJB 3.0 entity beans. Each of these cache services is defined in a separate Mbean, and each cache creates its own JGroups Channel. We will cover those MBeans when we discuss specific services in the next several sections.
 </para>
+</section>
 
-      <section id="clustering-intro-arch">
-        <title>Service Architectures</title>
-        <para>The clustering topography defined by the <literal>HAPartition</literal> MBean on each node is
-		of great importance to system administrators. But for most application developers, you are probably more concerned about the cluster architecture from a client application's point of view. Two basic clustering architectures are used with JBoss AS: client-side interceptors (a.k.a smart proxies or stubs) and external load balancers. Which architecture your application will use will depend on what type of client you have.
-	    </para>
+<section id="clustering-intro-arch">
+   <title>Service Architectures</title>
+   <para>The clustering topography defined by the <literal>HAPartition</literal> MBean on each node is
+	of great importance to system administrators. But for most application developers, you are probably more concerned about the cluster architecture from a client application's point of view. Two basic clustering architectures are used with JBoss AS: client-side interceptors (a.k.a smart proxies or stubs) and external load balancers. Which architecture your application will use will depend on what type of client you have.
+	</para>
 	    
 	    
         <section id="clustering-intro-arch-proxy">
@@ -175,8 +177,9 @@
         </section>
       
 </section>
-      <section id="clustering-intro-balancepolicy">
-        <title>Load-Balancing Policies</title>
+
+<section id="clustering-intro-balancepolicy">
+   <title>Load-Balancing Policies</title>
 	<para>
 		Both the JBoss client-side interceptor (stub) and load balancer use load balancing policies to determine which server node to which node a new request should be sent. In this section, let's go over the load balancing policies available in JBoss AS.
 	</para>
@@ -223,9 +226,9 @@
 	  
 	  
         </section>
-      </section>
+</section>
+     
       
-      
       <section id="clustering-intro-farm">
         <title>Farming Deployment</title>
         <para>The easiest way to deploy an application into the cluster is to use the farming service. That is
@@ -319,7 +322,6 @@
         </itemizedlist>
 
       </section>
-    </section>
 
 
       </chapter>