Author: clebert.suconic(a)jboss.com
Date: 2011-03-28 19:03:58 -0400 (Mon, 28 Mar 2011)
New Revision: 10404
Modified:
trunk/docs/user-manual/en/large-messages.xml
Log:
doc changes
Modified: trunk/docs/user-manual/en/large-messages.xml
===================================================================
--- trunk/docs/user-manual/en/large-messages.xml 2011-03-28 22:22:28 UTC (rev 10403)
+++ trunk/docs/user-manual/en/large-messages.xml 2011-03-28 23:03:58 UTC (rev 10404)
@@ -60,7 +60,7 @@
different physical volume to the message journal or paging
directory.</para>
</section>
<section>
- <title>Setting the limits</title>
+ <title>Configuring Parameters</title>
<para>Any message larger than a certain size is considered a large message.
Large messages
will be split up and sent in fragments. This is determined by the parameter
<literal
min-large-message-size</literal></para>
@@ -80,14
+80,6 @@
on how to instantiate the session factory.</para>
</section>
<section>
- <title>Compressed Large Messages</title>
- <para>If you specify the boolean property
<literal>compress-large-message</literal> on
- the <literal>server locator</literal> or
<literal>ConnectionFactory</literal> The
- system will use the ZIP algorithm to compress the message body as the
message is
- transfered to the server's side. Notice that there's no special
treatment at the
- server's side, all the compressing and uncompressing is done at the
client.</para>
- </section>
- <section>
<title>Using JMS</title>
<para>If JNDI is used to look up the connection factory, the minimum
large message size
is specified in
<literal>hornetq-jms.xml</literal></para>
@@ -108,6 +100,14 @@
message size is specified by <literal
HornetQConnectionFactory.setMinLargeMessageSize</literal>.</para>
</section>
+ <section>
+ <title>Compressed Large Messages</title>
+ <para>If you specify the boolean property
<literal>compress-large-message</literal> on
+ the <literal>server locator</literal> or
<literal>ConnectionFactory</literal> The
+ system will use the ZIP algorithm to compress the message body as the
message is
+ transfered to the server's side. Notice that there's no special
treatment at the
+ server's side, all the compressing and uncompressing is done at the
client.</para>
+ </section>
</section>
<section>
<title>Streaming large messages</title>