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:19:07 UTC

svn commit: r782276 - /websites/staging/river/trunk/content/river/concepts.html

Author: buildbot
Date: Fri Jan  7 13:19:06 2011
New Revision: 782276

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:19:06 2011
@@ -69,20 +69,25 @@
         <tr>
         <td style="overflow: hidden;" valign="top" width="100%">
           <div class="wiki-content">
+<h1 id="river">River</h1>
+<p>River is a toolkit to build distributed systems with. 
+The basic communication between client and service is based on RPC.</p>
 <h1 id="communication">Communication</h1>
-<p>Client and server communicate with a protocol called JERI. 
+<p>Client and service communicate with a protocol called JERI. 
 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.
+<p>The smallest river system is comprised of a service and a client.
 They only make use of JERI to communicate. No dynamic discovery is possible.</p>
-<p>The next system in size is a combination of a rpc-server, rpc-client and a registry. 
+<p>The next system in size is a combination of a service, client and a registry. 
 This allows for automatic discovery of client, server and registry. 
-The rpc-server provides services and registers them in the registry.</p>
-<p>For a system that also provides for downloadable code, you will need a rpc-server, 
-rpc-client, registry and codebase-server.</p>
-<h1 id="services">Services</h1>
-<p>...</p>
+The VM hosting the service registers the service in the registry.</p>
+<p>For a system that also provides for downloadable code, you will need a service, 
+client, registry and codebase-server.</p>
+<h1 id="basic_services">Basic services</h1>
+<p>There are several basic services. For locking, distributed events, leasing, transactions.</p>
+<h1 id="extended_services">Extended services</h1>
+<p>River has an implementation of 'Tuple spaces' called JavaSpaces.</p>
           </div>
         </td>
         <td valign="top">