You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airavata.apache.org by bu...@apache.org on 2012/07/06 16:14:47 UTC
svn commit: r824802 - in /websites/staging/airavata/trunk/content: ./
airavata/architecture/registry.html
Author: buildbot
Date: Fri Jul 6 14:14:47 2012
New Revision: 824802
Log:
Staging update by buildbot for airavata
Modified:
websites/staging/airavata/trunk/content/ (props changed)
websites/staging/airavata/trunk/content/airavata/architecture/registry.html
Propchange: websites/staging/airavata/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Jul 6 14:14:47 2012
@@ -1 +1 @@
-1358210
+1358222
Modified: websites/staging/airavata/trunk/content/airavata/architecture/registry.html
==============================================================================
--- websites/staging/airavata/trunk/content/airavata/architecture/registry.html (original)
+++ websites/staging/airavata/trunk/content/airavata/architecture/registry.html Fri Jul 6 14:14:47 2012
@@ -128,7 +128,8 @@ the generic JCR API and is integrated wi
GFac components to store and retrieve data. In addition to the service information, the registry is used to catalog workflow consumed inputs
and generated output data. The registry is also used to advertise and retrieve persistent service information. The use of the registry for
GFac service registration allows for late service binding and supporting large number of applications provided by the inherent load balance
-capabilities. </p>
+capabilities. For more up to date information and samples on Airavata API, refer [Client API Overview][api].</p>
+<p>[api] : https://cwiki.apache.org/confluence/display/AIRAVATA/Client+API+Overview</p>
</div>
<!--<div id="rightnav">