Author: buildbot
Date: Fri Dec 23 06:06:26 2016
New Revision: 1003319
Log:
Staging update by buildbot for river
Modified:
websites/staging/river/trunk/content/ (props changed)
websites/staging/river/trunk/content/index.html
Propchange: websites/staging/river/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Dec 23 06:06:26 2016
@@ -1 +1 @@
-1775684
+1775792
Modified: websites/staging/river/trunk/content/index.html
==============================================================================
--- websites/staging/river/trunk/content/index.html (original)
+++ websites/staging/river/trunk/content/index.html Fri Dec 23 06:06:26 2016
@@ -162,7 +162,7 @@ h2:hover > .headerlink, h3:hover > .head
<div class="row">
<div class="col-lg-6 col-sm-6 col-md-4 description-container">
<h4><i class="fa fa-exchange"></i> Communication</h4>
- Client and service communicate with a protocol called <a
href="/release-doc/2.2.3/api/net/jini/jeri/connection/doc-files/mux.html">JERI</a>.
+ Client and service communicate with a protocol called <a
href="/release-doc/2.2.2/api/net/jini/jeri/connection/doc-files/mux.html">JERI</a>.
JERI implementations are available for plain TCP, plain SSL,
HTTP, HTTPS and Kerberos TCP.
For compatibility with RMI there is also a JRMP transport.
<div class="space-sm"></div>
