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

[Ron Sigal]

  User: rsigal  
  Date: 06/08/01 23:24:17

  Modified:    docs/guide/en  chap3.xml
  Log:
  JBREM-559:  Expanded discussion of InvokerLocator comparison operators.
  
  Revision  Changes    Path
  1.4       +14 -18    JBossRemoting/docs/guide/en/chap3.xml
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: chap3.xml
  ===================================================================
  RCS file: /cvsroot/jboss/JBossRemoting/docs/guide/en/chap3.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -b -r1.3 -r1.4
  --- chap3.xml	1 Aug 2006 23:23:14 -0000	1.3
  +++ chap3.xml	2 Aug 2006 03:24:17 -0000	1.4
  @@ -19,7 +19,7 @@
     InvokerLocator string socket://192.168.10.1:8080 describes a TCP/IP
     Socket-based transport, which is listening on port 8080 of the IP address,
     192.168.10.1. Using the string URI, or the InvokerLocator object,
  -  JBossRemoting can make a client connection to the remote JBoss server. The
  +  JBossRemoting can make a client connection to the remote server. The
     format of the locator string is the same as the URI type:
     <code>[transport]://[host]:&lt;port&gt;/path/?&lt;parameter=value&gt;&amp;&lt;parameter=value&gt;</code></para>
   
  @@ -32,27 +32,23 @@
     use).</para>
   
     <para>The InvokerLocator will accept host name as is and will not
  -  automatically convert to ip address (since 2.0.0 release). This means
  -  equality for locators is based on if is host name or ip, but does not
  -  resolve one to the other. The following is a list of how the InvokerLocator
  -  will evaluate equality between two instances based on the locator uri string
  -  passed: </para>
  +  automatically convert to IP address (since 2.0.0 release). There are two
  +  comparison operators for InvocatorLocators, <methodname>equals()</methodname>
  +  and <methodname>isSameEndpoint()</methodname>, and neither resolve a hostname
  +  to IP address or vice versa.  <methodname>equals()</methodname> compares all
  +  components of the InvokerLocator, character by character, while
  +  <methodname>isSameEndpoint()</methodname> uses only protocol, host, and port. 
  +  The following examples are just some of the comparisons that can be seen in
  +  <classname>org.jboss.test.remoting.locator.InvokerLocatorTestCase</classname>:
  +  </para>
   
  -  <para>InvokerLocator.equals(): </para>
  +  <para><code>new InvokerLocator("http://localhost:1234/services/uri:Test").equals(new InvokerLocator("http://localhost:1234"))</code> returns false</para>
   
  -  <para>http://localhost:1234/services/uri:Test &amp; http://localhost:1234 =
  -  false </para>
  +  <para><code>new InvokerLocator("http://localhost:1234/services/uri:Test").equals(new InvokerLocator("http://127.0.0.1:1234"))</code> returns false</para>
   
  -  <para>http://localhost:1234/services/uri:Test &amp; http://127.0.0.1:1234 =
  -  false </para>
  +  <para><code>new InvokerLocator("http://localhost:1234/services/uri:Test").isSameEndpoint(new InvokerLocator("http://localhost:1234"))</code> returns true </para>
   
  -  <para>InvokerLocator.isSameEndpoint(): </para>
  -
  -  <para>http://localhost:1234/services/uri:Test &amp; http://localhost:1234 =
  -  true </para>
  -
  -  <para>http://localhost:1234/services/uri:Test &amp; http://127.0.0.1:1234 =
  -  false</para>
  +  <para><code>new InvokerLocator("http://localhost:1234/services/uri:Test").isSameEndpoint(new InvokerLocator("http://127.0.0.1:1234"))</code> returns false</para>
   
     <para><emphasis
     role="bold">org.jboss.remoting.transport.Connector</emphasis> - is an MBean