You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by bu...@apache.org on 2011/01/07 14:03:19 UTC
svn commit: r782272 -
/websites/staging/river/trunk/content/river/concepts.html
Author: buildbot
Date: Fri Jan 7 13:03:18 2011
New Revision: 782272
Log:
Staging update by buildbot
Modified:
websites/staging/river/trunk/content/river/concepts.html
Modified: websites/staging/river/trunk/content/river/concepts.html
==============================================================================
--- websites/staging/river/trunk/content/river/concepts.html (original)
+++ websites/staging/river/trunk/content/river/concepts.html Fri Jan 7 13:03:18 2011
@@ -71,7 +71,8 @@
<div class="wiki-content">
<h1 id="communication">Communication</h1>
<p>Client and server communicate with a protocol called JERI.
-There are JERI implementations for plain-tcp, plain-ssl, http, https and kerberos-tcp.</p>
+There are JERI implementations for plain-TCP, plain-SSL, HTTP, HTTPS and Kerberos-TCP.
+For compatibility with RMI there is also a JRMP transport.</p>
<h1 id="from_small_to_big">From small to big</h1>
<p>The smallest river system is comprised of a rpc-server and a rpc-client.
They only make use of JERI to communicate. No dynamic discovery is possible.</p>