[jboss-cvs] jboss-seam/doc/reference/en/modules ...

[Peter Muir]

  User: pmuir   
  Date: 07/09/04 17:07:54

  Modified:    doc/reference/en/modules  conversations.xml
  Log:
  Better descriptions of a4j options
  
  Revision  Changes    Path
  1.36      +20 -4     jboss-seam/doc/reference/en/modules/conversations.xml
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: conversations.xml
  ===================================================================
  RCS file: /cvsroot/jboss/jboss-seam/doc/reference/en/modules/conversations.xml,v
  retrieving revision 1.35
  retrieving revision 1.36
  diff -u -b -r1.35 -r1.36
  --- conversations.xml	4 Sep 2007 17:00:40 -0000	1.35
  +++ conversations.xml	4 Sep 2007 21:07:52 -0000	1.36
  @@ -998,14 +998,30 @@
           </listitem>
           <listitem>
             <para>
  -            <literal>ignoreDupRequests</literal> &#8212; if a duplicate request
  -            occurs, the unfinished event will be aborted
  +            <literal>ignoreDupResponses</literal> &#8212; ignore the response 
  +            produced by the request if a more recent 'similar' request is
  +            already in the queue. ignoreDupResponses="true" does <emphasis>not 
  +            cancel</emphasis> the the processing of the request on the server
  +            side &#8212; just prevents unnecessary updates on the client side.
  +          </para>
  +          <para>
  +            This option should be used with care with Seam's conversations as
  +            it allows multiple concurrent requests to be made.
             </para>
           </listitem>
           <listitem>
             <para>
  -            <literal>requestDelay</literal> &#8212; Delays the sending of the
  -            request to the server
  +            <literal>requestDelay</literal> &#8212; defines the time (in ms.)
  +            that the request will be remain on the queue. If the request has
  +            not been processed by after this time the request will be sent 
  +            (regardless of whether a response has been received) or discarded
  +            (if there is a more recent similar event on the queue).
  +          </para>
  +          <para>
  +            This option should be used with care with Seam's conversations as
  +            it allows multiple concurrent requests to be made.  You need to be
  +            sure that the delay you set (in combination with the concurrent
  +            request timeout) is longer than the action will take to execute.
             </para>
           </listitem>
           <listitem>