You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@avalon.apache.org by le...@apache.org on 2003/01/14 06:21:30 UTC

cvs commit: jakarta-avalon-excalibur/altrmi/src/xdocs transports.xml

leif        2003/01/13 21:21:30

  Modified:    altrmi/src/xdocs transports.xml
  Log:
  Fix a couple minor typos
  
  Revision  Changes    Path
  1.7       +5 -5      jakarta-avalon-excalibur/altrmi/src/xdocs/transports.xml
  
  Index: transports.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-avalon-excalibur/altrmi/src/xdocs/transports.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- transports.xml	12 Dec 2002 07:56:59 -0000	1.6
  +++ transports.xml	14 Jan 2003 05:21:30 -0000	1.7
  @@ -18,14 +18,14 @@
         <p>
           The supplied transports fall into two categories - Intra-JVM and Inter-JVM. The Inter-JVM types are for
           bridging a network divide over TCP/IP.  This can also mean two JVMs in the same physical machine, using
  -        local-loop TCP/IP. The Intra-JVM types are dor situations where normal dynamic proxy will not work.  For
  -        example when the client and the server both have a definition of the same interfact in different
  +        local-loop TCP/IP. The Intra-JVM types are for situations where normal dynamic proxy will not work.  For
  +        example when the client and the server both have a definition of the same interface in different
           classloaders.  Most Java projects do not involve trees of classloaders, but writing frameworks like
           Avalon-Phoenix or or an implementation of the EJB specification will.
         </p>
         <p>
  -        All of these transports are synchronous too.  That means that an invocation acorss there connection
  -        will wait until the it is completed server side before the next invocation is allowed through.
  +        All of these transports are synchronous too.  That means that an invocation across their connection
  +        will wait until it is completed server side before the next invocation is allowed through.
         </p>
   
         <s2 title="Plain Sockets / ObjectStream &amp; CustomStream varients">
  
  
  

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>