svn commit: r927503 - in /websites/staging/directory/trunk/content: ./ fortress/user-guide/2.2-tradi-multi-instances.html

[bu...@apache.org]

Author: buildbot
Date: Fri Oct 31 13:42:14 2014
New Revision: 927503

Log:
Staging update by buildbot for directory

Modified:
    websites/staging/directory/trunk/content/   (props changed)
    websites/staging/directory/trunk/content/fortress/user-guide/2.2-tradi-multi-instances.html

Propchange: websites/staging/directory/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Oct 31 13:42:14 2014
@@ -1 +1 @@
-1634924
+1635772

Modified: websites/staging/directory/trunk/content/fortress/user-guide/2.2-tradi-multi-instances.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/user-guide/2.2-tradi-multi-instances.html (original)
+++ websites/staging/directory/trunk/content/fortress/user-guide/2.2-tradi-multi-instances.html Fri Oct 31 13:42:14 2014
@@ -177,7 +177,7 @@
 <p>(From Wikipedia)</p>
 <p>Multitenancy refers to a principle in software architecture where a single instance of the software runs on a server, serving multiple client organizations (tenants). Multitenancy is contrasted with a multi-instance architecture where separate software instances (or hardware systems) are set up for different client organizations. With a multitenant architecture, a software application is designed to virtually partition its data and configuration, and each client organization works with a customized virtual application instance.</p>
 <p>Multitenancy is also regarded as one of the essential attributes of cloud computing.[1]</p>
-<h2 id="after-fortress">After Fortress</h2>
+<h2 id="before-fortress">Before Fortress</h2>
 <p>Client data had to be maintained on separate instances of LDAP server.</p>
 <p><img alt="Multitenancy" src="images/MultiInstance-TraditionalNetworkDiagram2.png" /></p>