[jboss-cvs] JBossRemoting/docs/guide/en ...

[Ron Sigal]

  User: rsigal  
  Date: 07/03/15 19:47:38

  Modified:    docs/guide/en  Tag: remoting_2_x chap5.xml
  Log:
  JBREM-634, JBREM-726, JBREM-727: (1) Added bisocket parameter MAX_RETRIES; (2) added discussion about retrieving implicitly created callback Connectors.
  
  Revision  Changes    Path
  No                   revision
  
  
  No                   revision
  
  
  1.12.2.9  +74 -0     JBossRemoting/docs/guide/en/chap5.xml
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: chap5.xml
  ===================================================================
  RCS file: /cvsroot/jboss/JBossRemoting/docs/guide/en/chap5.xml,v
  retrieving revision 1.12.2.8
  retrieving revision 1.12.2.9
  diff -u -b -r1.12.2.8 -r1.12.2.9
  --- chap5.xml	13 Mar 2007 01:55:54 -0000	1.12.2.8
  +++ chap5.xml	15 Mar 2007 23:47:38 -0000	1.12.2.9
  @@ -2637,6 +2637,16 @@
             connection.  In particular, the window is ping frequency * ping window factor.
             See also the definition of PING_FREQUENCY. The default value is 2.
           </para>
  +        
  +        <para>
  +          <emphasis role="bold">MAX_RETRIES </emphasis> (actual value is
  +          "maxRetries"): This parameter is relevant only on the client side,
  +          where the <classname>BisocketClientInvoker</classname> uses it
  +          to govern the number of attempts it should make to get the address and
  +          port of the secondary <classname>ServerSocket</classname>, and the
  +          <classname>BisocketServerInvoker</classname> uses it to govern the
  +          number of attempts it should make to create both ordinary and control
  +          sockets. The default value is 10. </para>
         </section>
         
         <section>
  @@ -3591,6 +3601,70 @@
           </para>
           
           <para>
  +          The implicitly created callback <classname>Connectors</classname> are
  +          available for reuse. Each <classname>Client</classname> maintains a
  +          set of all callback <classname>Connector</classname>s it has implicitly
  +          created for each <classname>InvokerCallbackHandler</classname> that is
  +          passed in by way of one of the <methodname>addListener()</methodname>
  +          methods. For example,
  +        </para>
  +        
  +        <programlisting>
  +        InvokerCallbackHandler callbackHandler = new SampleCallbackHandler();
  +        client.addListener(callbackHandler, new HashMap(), null, true);
  +        client.addListener(callbackHandler, new HashMap(), null, true);
  +        </programlisting>
  +        
  +        <para>
  +          would result in a set of two callback
  +          <classname>Connector</classname>s associated with
  +          <code>callbackHandler</code>.  These sets of callback
  +          <classname>Connector</classname>s are accessible by way of the
  +          <classname>Client</classname> method
  +        </para>
  +        
  +        <programlisting>
  +        public Set getCallbackConnectors(InvokerCallbackHandler callbackHandler);
  +        </programlisting>
  +        
  +        <para>
  +          A callback <classname>Connector</classname> could be reused as in the
  +          following code:
  +        </para>
  +        
  +        <programlisting>
  +        InvokerCallbackHandler callbackHandler1 = new SampleCallbackHandler();
  +        client.addListener(callbackHandler1, new HashMap(), null, true);
  +        Set callbackConnectors = client.getCallbackConnectors(callbackHandler1);
  +        Connector callbackConnector = (Connector) callbackConnectors.iterator().next();
  +        InvokerCallbackHandler callbackHandler2 = new SampleCallbackHandler();
  +        client.addListener(callbackHandler2, callbackConnector.getLocator());
  +        </programlisting>
  +        
  +        <para>
  +          which would result in the implicitly created callback
  +          <classname>Connector</classname> having two registered
  +          <classname>InvokerCallbackHandler</classname>s.  Note, by the way, that
  +          if the <classname>InvokerCallbackHandler</classname> were reused as in
  +          the following:
  +        </para>
  +        
  +        <programlisting>
  +        InvokerCallbackHandler callbackHandler1 = new SampleCallbackHandler();
  +        client.addListener(callbackHandler1, new HashMap(), null, true);
  +        Set callbackConnectors = client.getCallbackConnectors(callbackHandler1);
  +        Connector callbackConnector = (Connector) callbackConnectors.iterator().next();
  +        client.addListener(callbackHandler1, callbackConnector.getLocator());
  +        </programlisting>
  +        
  +        <para>
  +          then only one callback connection would be created, because a single
  +          (<classname>Connector</classname>,
  +          <classname>InvokerCallbackHandler</classname>) pair can be associated
  +          with only one callback connection.
  +        </para>
  +        
  +        <para>
             There are six parameters that can be passed to
             <methodname>addListener()</methodname> in the <code>metadata</code>
             map which are specific to push callback configuration. The first three