river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r782277 - /websites/staging/river/trunk/content/river/concepts.html
Date Fri, 07 Jan 2011 13:24:47 GMT
Author: buildbot
Date: Fri Jan  7 13:24:46 2011
New Revision: 782277

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:24:46 2011
@@ -80,9 +80,9 @@ For compatibility with RMI there is also
 <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 service, client and a registry. 
-This allows for automatic discovery of client, server and registry. 
+This allows for automatic discovery of client, service and registry. 
 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,

+<p>For a system that also provides for ondemand distribution of compiled 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>



Mime
View raw message