[jboss-remoting-commits] JBoss Remoting SVN: r4991 - remoting2/branches/2.2/docs/guide/en.
jboss-remoting-commits at lists.jboss.org
jboss-remoting-commits at lists.jboss.org
Tue Apr 14 02:29:01 EDT 2009
Author: ron.sigal at jboss.com
Date: 2009-04-14 02:29:01 -0400 (Tue, 14 Apr 2009)
New Revision: 4991
Modified:
remoting2/branches/2.2/docs/guide/en/chap10.xml
Log:
JBREM-1103: Updated oneway invocation example.
Modified: remoting2/branches/2.2/docs/guide/en/chap10.xml
===================================================================
--- remoting2/branches/2.2/docs/guide/en/chap10.xml 2009-04-14 06:28:34 UTC (rev 4990)
+++ remoting2/branches/2.2/docs/guide/en/chap10.xml 2009-04-14 06:29:01 UTC (rev 4991)
@@ -289,6 +289,13 @@
worker thread on the client side will make the actual invocation on the
server. This is faster of the two modes, but if there is a problem making
the request on the server, the original caller will be unaware.</para>
+
+ <para><emphasis role="bold">NOTE.</emphasis> In the interest of performance,
+ the behavior of the various transports is not required to conform to the
+ preceding description of the first, "server side", mode, in which the invocation
+ is made on the calling thread. In particular, the socket and bisocket transports
+ return immediately after writing the invocation, without waiting for a
+ response from the server.</para>
<para>The OnewayServer is exactly the same as the SimpleServer from the
previous example, with the exception that invocation handler returns null
More information about the jboss-remoting-commits
mailing list