river-commits mailing list archives

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

URL: http://svn.apache.org/viewvc?rev=1056299&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=1056299&r1=1056298&r2=1056299&view=diff
==============================================================================
--- incubator/river/site/trunk/content/river/concepts.mdtext (original)
+++ incubator/river/site/trunk/content/river/concepts.mdtext Fri Jan  7 13:01:34 2011
@@ -20,3 +20,14 @@ Notice:    Licensed to the Apache Softwa
 Client and server communicate with a protocol called JERI. 
 There are JERI implementations for plain-tcp, plain-ssl, http, https and kerberos-tcp.
 
+# From small to big
+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.
+
+The next system in size is a combination of a rpc-server, rpc-client and a registry. 
+
+For a system that also provides for downloadable code, you will need a rpc-server, 
+rpc-client, registry and codebase-server.
+
+# Services
+...



Mime
View raw message