Author: buildbot
Date: Wed May 22 12:40:52 2013
New Revision: 862738
Log:
Staging update by buildbot for sling
Modified:
websites/staging/sling/trunk/content/ (props changed)
websites/staging/sling/trunk/content/documentation/bundles/discovery-api-and-impl.html
Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed May 22 12:40:52 2013
@@ -1 +1 @@
-1485185
+1485192
Modified:
websites/staging/sling/trunk/content/documentation/bundles/discovery-api-and-impl.html
==============================================================================
---
websites/staging/sling/trunk/content/documentation/bundles/discovery-api-and-impl.html
(original)
+++
websites/staging/sling/trunk/content/documentation/bundles/discovery-api-and-impl.html
Wed May 22 12:40:52 2013
@@ -185,13 +185,13 @@ meant to be used to announce configurati
<h2 id="deployment-and-configuration">Deployment and configuration</h2>
-<p>The discovery API makes no assumptions as to how the instances and clusters
discovery each other. This is entirely
+<p>The discovery API makes no assumptions as to how the instances and clusters
discover each other. This is entirely
up to the implementations. Some might choose automatic discovery within a LAN
using IP multicast, others
might choose explicit configuration via a central service etc.</p>
<h2 id="discoveryimpl-resource-based-ootb-implementation">discovery.impl:
Resource-based, OOTB Implementation</h2>
-<p>The <code>discovery.impl</code> bundle is a resource-based, out of the box
implementation using standard Sling. The discovery within
-a cluster is done by writing heartbeat information into the (common)
repository. The establishment of a clusterview
-is done by analyzing these heartbeats, initiating a voting within the cluster
(such that each instance can agree
+<p>The <code>discovery.impl</code> bundle is a resource-based, out of the box
implementation of the <code>discovery.api</code> using standard Sling.
+The discovery within a cluster is done by writing heartbeat information into
the (common) repository. The establishment of a
+clusterview is done by analyzing these heartbeats, initiating a voting within
the cluster (such that each instance can agree
that it sees the same number of instances) and by concluding the voting by
promoting it as the new "established" view.</p>
<h3 id="location-in-repository">Location in Repository</h3>
<p>Administrative note: All the information about the topology is stored at
the following location in the repository:</p>
@@ -237,7 +237,7 @@ that it sees the same number of instance
</li>
</ul>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1485185 by bdelacretaz on Wed, 22 May 2013 12:26:37 +0000
+ Rev. 1485192 by stefanegli on Wed, 22 May 2013 12:40:46 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
