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

[bu...@apache.org]

Author: buildbot
Date: Fri Jan  7 13:06:28 2011
New Revision: 782274

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:06:28 2011
@@ -76,7 +76,9 @@ For compatibility with RMI there is also
 <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>
-<p>The next system in size is a combination of a rpc-server, rpc-client and a registry. </p>
+<p>The next system in size is a combination of a rpc-server, rpc-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>