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

[Gavin King]

  User: gavin   
  Date: 06/11/20 14:24:18

  Modified:    doc/reference/en  master.xml
  Log:
  updates
  
  Revision  Changes    Path
  1.43      +12 -2     jboss-seam/doc/reference/en/master.xml
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: master.xml
  ===================================================================
  RCS file: /cvsroot/jboss/jboss-seam/doc/reference/en/master.xml,v
  retrieving revision 1.42
  retrieving revision 1.43
  diff -u -b -r1.42 -r1.43
  --- master.xml	19 Nov 2006 16:27:38 -0000	1.42
  +++ master.xml	20 Nov 2006 19:24:18 -0000	1.43
  @@ -61,13 +61,23 @@
                   </listitem>
               </varlistentry>
               <varlistentry>
  -                <term><emphasis>Integrated AJAX-based Remoting</emphasis></term>
  +                <term><emphasis>Integrated AJAX</emphasis></term>
                   <listitem>
                       <para>
  -                        Seam provides a built-in JavaScript remoting layer for EJB3 components. AJAX clients 
  +                        Seam supports two open source JSF-based AJAX solutions: ICEfaces and Ajax4JSF. These
  +                        solutions let you add AJAX capability to your user interface without the need to
  +                        write any JavaScript code.
  +                    </para>
  +                    <para>
  +                        Seam also provides a built-in JavaScript remoting layer for EJB3 components. AJAX clients 
                           can easily call server-side components and subscribe to JMS topics, without the need 
                           for an intermediate action layer.
                       </para>
  +                    <para>
  +                        Neither of these approaches would work well, were it not for Seam's built-in concurrency 
  +                        and state management, which ensures that many concurrent fine-grained, asynchronous AJAX 
  +                        requests are handled safely and efficiently on the server side
  +                    </para>
                   </listitem>
               </varlistentry>
               <varlistentry>