[jboss-cvs] JBossAS SVN: r103395 - projects/docs/enterprise/5.0.1/Administration_And_Configuration_Guide/en-US.

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

Author: laubai
Date: 2010-04-01 02:47:54 -0400 (Thu, 01 Apr 2010)
New Revision: 103395

Modified:
   projects/docs/enterprise/5.0.1/Administration_And_Configuration_Guide/en-US/Clustering_Guide_HTTP.xml
Log:
JBPAPP-2646 Corrected use of AS and worker.node2.host.

Modified: projects/docs/enterprise/5.0.1/Administration_And_Configuration_Guide/en-US/Clustering_Guide_HTTP.xml
===================================================================
--- projects/docs/enterprise/5.0.1/Administration_And_Configuration_Guide/en-US/Clustering_Guide_HTTP.xml	2010-04-01 06:43:47 UTC (rev 103394)
+++ projects/docs/enterprise/5.0.1/Administration_And_Configuration_Guide/en-US/Clustering_Guide_HTTP.xml	2010-04-01 06:47:54 UTC (rev 103395)
@@ -180,7 +180,7 @@
 # Define Node2
 # modify the host as your host IP or DNS name.
 worker.node2.port=8009
-worker.node2.host= node2.mydomain.com
+worker.node2.host=node2.mydomain.com
 worker.node2.type=ajp13
 worker.node2.ping_mode=A
 worker.node2.lbfactor=1
@@ -406,7 +406,7 @@
         and needs to be replicated. This element has 3 valid values:</para>
         <itemizedlist>
           <listitem>
-		  <para><emphasis role="bold">SET_AND_GET</emphasis> is conservative but not optimal (performance-wise): it will always replicate session data even if its content has not been modified but simply accessed. This setting made (a little) sense in AS 4 since using it was a way to ensure that every request triggered replication of the session's timestamp. Since setting <literal>max_unreplicated_interval</literal> to 0 accomplishes the same thing at much lower cost, using <literal>SET_AND_GET</literal> makes no sense with Enterprise Application Platform 5.</para>
+		  <para><emphasis role="bold">SET_AND_GET</emphasis> is conservative but not optimal (performance-wise): it will always replicate session data even if its content has not been modified but simply accessed. This setting made (a little) sense in JBoss Enterprise Application Platform 4 since using it was a way to ensure that every request triggered replication of the session's timestamp. Since setting <literal>max_unreplicated_interval</literal> to 0 accomplishes the same thing at much lower cost, using <literal>SET_AND_GET</literal> makes no sense with Enterprise Application Platform 5.</para>
           </listitem>
           <listitem>
 		  <para><emphasis role="bold">SET_AND_NON_PRIMITIVE_GET</emphasis> is conservative but will only replicate if an object of a non-primitive type has been accessed (i.e. the object is not of a well-known immutable JDK type such as <literal>Integer</literal>, <literal>Long</literal>, <literal>String</literal>, etc.) This is the default value.</para>