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

[Tom Elrod]

  User: telrod  
  Date: 06/07/25 17:19:22

  Modified:    docs/guide/en  master.xml
  Log:
  JBREM-383 - added short versioning section to remoting docs.
  
  Revision  Changes    Path
  1.26      +27 -9     JBossRemoting/docs/guide/en/master.xml
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: master.xml
  ===================================================================
  RCS file: /cvsroot/jboss/JBossRemoting/docs/guide/en/master.xml,v
  retrieving revision 1.25
  retrieving revision 1.26
  diff -u -b -r1.25 -r1.26
  --- master.xml	24 Jul 2006 06:15:59 -0000	1.25
  +++ master.xml	25 Jul 2006 21:19:22 -0000	1.26
  @@ -466,32 +466,32 @@
   
       <para><emphasis role="bold">jboss-remoting-socket.jar</emphasis> -
       contains all the classes needed for the socket and sslsocket transports to
  -    function as both a client and a server. </para>
  +    function as both a client and a server.</para>
   
       <para><emphasis><emphasis
       role="bold">jboss-remoting-socket-client.jar</emphasis></emphasis> -
       contains all the classes needed for the socket and sslsocket transports to
       function as a client only. This means will not be able to perform any push
  -    callbacks or sending of streams using this jar. </para>
  +    callbacks or sending of streams using this jar.</para>
   
       <para><emphasis role="bold">jboss-remoting-http.jar</emphasis> - contains
       all the classes needed for the http and https transports to function as a
  -    client and a server. </para>
  +    client and a server.</para>
   
       <para><emphasis role="bold">jboss-remoting-http-client.jar</emphasis> -
       contains all the classes needed for the http, https, servlet, and
       sslservlet transports to function as a client only. This means will not be
  -    able to perform any push callbacks or sending of streams using this jar.
  -    </para>
  +    able to perform any push callbacks or sending of streams using this
  +    jar.</para>
   
       <para><emphasis role="bold">jboss-remoting-servlet.jar</emphasis> -
       contains all the classes needed for the servlet or sslservlet transports
       to function as a server only (also requires servlet-invoker.war be
  -    deployed within web container as well) </para>
  +    deployed within web container as well)</para>
   
       <para><emphasis role="bold">jboss-remoting-rmi.jar</emphasis> - contains
       all the classes needed for the rmi and sslrmi transports to function as a
  -    client and a server. </para>
  +    client and a server.</para>
   
       <para><emphasis role="bold">jboss-remoting-multiplex.jar</emphasis> -
       contains all the classes needed for the multiplex and sslmultiplex
  @@ -6026,6 +6026,24 @@
     </chapter>
   
     <chapter>
  +    <title>Compatibility and versioning</title>
  +
  +    <para>As of JBossRemoting 2.0.0 versioning has been added to guarantee
  +    compatibility between different versions. This is accomplished by changing
  +    serialization formats for certain classes and by using wire versioing. By
  +    wire versioning, mean that the version used by a client and server will be
  +    sent on the wire so that the other side will be able to adjust
  +    accordingly. This will be automatic for JBossRemoting 2.0.0 and later
  +    versions. However, since versioning was not introduced until the 2.0.0
  +    release, if need to have a 1.4.x version of remoting communicate to a
  +    later version, will need to set a system property on the 2.0.0 version so
  +    that knows to use the older wire protocol version. The system property to
  +    set is 'jboss.remoting.pre_2_0_compatible' and should be set to true.
  +    There are a few minor features that will not be fully compatible between
  +    1.4.x release and 2.0.0, which are listed in the release notes.</para>
  +  </chapter>
  +
  +  <chapter>
       <title>Getting the JBossRemoting source and building</title>
   
       <para>The JBossRemoting source code resides in the JBoss CVS repository