Author: msorokin
Date: 2009-04-22 08:23:19 -0400 (Wed, 22 Apr 2009)
New Revision: 13759
Modified:
trunk/docs/userguide/en/src/main/docbook/included/queue.xml
Log:
https://jira.jboss.org/jira/browse/RF-5952
New functionality of ignoreDupResponses is documented
Modified: trunk/docs/userguide/en/src/main/docbook/included/queue.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/queue.xml 2009-04-22 11:38:59 UTC
(rev 13758)
+++ trunk/docs/userguide/en/src/main/docbook/included/queue.xml 2009-04-22 12:23:19 UTC
(rev 13759)
@@ -119,8 +119,9 @@
</para>
<para>
- The
<emphasis><property>"ignoreDupResponses"</property></emphasis>
attribute that takes a boolean value can also help optimize your Ajax requests. The idea
of the attribute is to cancel
- similar events and send the latest one to the server. This works only if
similar events come sequentially.
+ The
<emphasis><property>"ignoreDupResponses"</property></emphasis>
attribute that takes a boolean value can also help optimize your Ajax requests.
+ If set to true, response processing for request will not occur if a similar
request is already waiting in the queue. New request will be fired immediately when the
response from the previous one returns.
+
</para>
<para>
@@ -137,7 +138,7 @@
<para>In this example, the requests are glued together and only the last
one is submitted.</para>
- <para>Another key attribute that easies revers load is
<emphasis><property
+ <para>Another key attribute that easies server load is
<emphasis><property
"timeout"</property></emphasis>.
The attribute specifies the amount of time an item can be in the queue before
the sent event is be aborted and dropped from the queue.
</para>