river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sijs...@apache.org
Subject svn commit: r1056304 - /incubator/river/site/trunk/content/river/concepts.mdtext
Date Fri, 07 Jan 2011 13:06:11 GMT
Author: sijskes
Date: Fri Jan  7 13:06:11 2011
New Revision: 1056304

URL: http://svn.apache.org/viewvc?rev=1056304&view=rev
Log:
CMS commit to river by sijskes

Modified:
    incubator/river/site/trunk/content/river/concepts.mdtext

Modified: incubator/river/site/trunk/content/river/concepts.mdtext
URL: http://svn.apache.org/viewvc/incubator/river/site/trunk/content/river/concepts.mdtext?rev=1056304&r1=1056303&r2=1056304&view=diff
==============================================================================
--- incubator/river/site/trunk/content/river/concepts.mdtext (original)
+++ incubator/river/site/trunk/content/river/concepts.mdtext Fri Jan  7 13:06:11 2011
@@ -26,6 +26,8 @@ The smallest river system is comprised o
 They only make use of JERI to communicate. No dynamic discovery is possible.
 
 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.
 
 For a system that also provides for downloadable code, you will need a rpc-server, 
 rpc-client, registry and codebase-server.



Mime
View raw message