Author: buildbot
Date: Wed Nov 25 16:59:14 2015
New Revision: 973553

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 Nov 25 16:59:14 2015
@@ -1 +1 @@
-1716480
+1716485

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 Nov 25 16:59:14 2015
@@ -122,7 +122,7 @@ access to the current topology, allows t
 instances) and contains a simple property exchange mechanism, e.g. to allow 
building communication services on top of it.</p>
 <div class="toc">
 <ul>
-<li><a href="#api">API</a><ul>
+<li><a href="#discovery-entities">Discovery Entities</a><ul>
 <li><a href="#instance-instancedescription">Instance, 
InstanceDescription</a></li>
 <li><a href="#cluster-clusterview">Cluster, ClusterView</a></li>
 <li><a href="#topology-topologyview">Topology, TopologyView</a></li>
@@ -142,20 +142,24 @@ instances) and contains a simple propert
 </li>
 </ul>
 </div>
-<h2 id="api">API<a class="headerlink" href="#api" title="Permanent 
link">&para;</a></h2>
+<h2 id="discovery-entities">Discovery Entities<a class="headerlink" 
href="#discovery-entities" title="Permanent link">&para;</a></h2>
 <p>The Discovery API defines the following entities</p>
 <h3 id="instance-instancedescription">Instance, InstanceDescription<a 
class="headerlink" href="#instance-instancedescription" title="Permanent 
link">&para;</a></h3>
-<p>A Sling instance running in one VM is represented in the discovery API by 
an <code>InstanceDescription</code>:
-<em> it represents one Sling instance
-</em> it has thus a unique Sling ID
-<em> it has a flag that marks if it is leader in a cluster (more details below)
-</em> plus it has properties (which can be provided via 
<code>PropertyProviders</code>)</p>
+<p>A Sling instance running in one VM is represented in the discovery API by 
an <code>InstanceDescription</code>:</p>
+<ul>
+<li>it represents one Sling instance</li>
+<li>it has thus a unique Sling ID</li>
+<li>it has a flag that marks if it is leader in a cluster (more details 
below)</li>
+<li>plus it has properties (which can be provided via 
<code>PropertyProviders</code>)</li>
+</ul>
 <h3 id="cluster-clusterview">Cluster, ClusterView<a class="headerlink" 
href="#cluster-clusterview" title="Permanent link">&para;</a></h3>
 <p>Multiple instances that are connected to the same underlying repository are 
commonly referred to as a 'Cluster'. The reasoning behind this terminology 
being that they access the same data and can thus deliver or modify the same 
data.</p>
-<p>In the discovery API this cluster concept is represented via a 
<code>ClusterView</code> object. A 'view' because it is a momentary snapshot of 
the cluster and only contains instances that are currently alive. It's features 
are:
-<em> each cluster has a stable leader. Stable meaning it won't change unless 
that leader crashes.
-</em> it has a list of instances that are part of it, thus currently alive
-* plus it has a unique id that is persistent across restarts</p>
+<p>In the discovery API this cluster concept is represented via a 
<code>ClusterView</code> object. A 'view' because it is a momentary snapshot of 
the cluster and only contains instances that are currently alive. It's features 
are:</p>
+<ul>
+<li>each cluster has a stable leader. Stable meaning it won't change unless 
that leader crashes.</li>
+<li>it has a list of instances that are part of it, thus currently alive</li>
+<li>plus it has a unique id that is persistent across restarts</li>
+</ul>
 <h3 id="topology-topologyview">Topology, TopologyView<a class="headerlink" 
href="#topology-topologyview" title="Permanent link">&para;</a></h3>
 <p>The topology - or more precisely the <code>TopologyView</code> - represents 
a snapshot (<code>view</code>) of a number of loosely coupled Sling instances 
(<code>InstanceDescription</code>)
 and clusters (<code>ClusterView</code>) of a particular deployment. A cluster 
can consist of one or more instances. Each instance
@@ -342,7 +346,7 @@ They use the same interval and timeout a
 </li>
 </ul>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; 
text-align: right;">
-        Rev. 1716480 by stefanegli on Wed, 25 Nov 2015 16:43:10 +0000
+        Rev. 1716485 by stefanegli on Wed, 25 Nov 2015 16:59:06 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Sling, Sling, Apache, the Apache feather logo, and the Apache 
Sling project


Reply via email to