svn commit: r1716642 - /sling/site/trunk/content/documentation/bundles/discovery-api-and-impl.mdtext

[st...@apache.org]

Author: stefanegli
Date: Thu Nov 26 13:33:57 2015
New Revision: 1716642

URL: http://svn.apache.org/viewvc?rev=1716642&view=rev
Log:
no-jira : adjusted wording

Modified:
    sling/site/trunk/content/documentation/bundles/discovery-api-and-impl.mdtext

Modified: sling/site/trunk/content/documentation/bundles/discovery-api-and-impl.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/discovery-api-and-impl.mdtext?rev=1716642&r1=1716641&r2=1716642&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/bundles/discovery-api-and-impl.mdtext (original)
+++ sling/site/trunk/content/documentation/bundles/discovery-api-and-impl.mdtext Thu Nov 26 13:33:57 2015
@@ -306,16 +306,18 @@ becomes unreliable. The eventual-ness of
 initiated from instance A is visible by instance B. And when there are no hard guarantees, it becomes impossible to choose
 a `heartbeatTimeout` that works for all eventualities.
 
-Therefore it becomes necessary to be able to store heartbeats in a repository that provides higher consistency (than eventualness).
-Such a 'low-level repository' is the DocumentStore of oak (which is an internal API of the DocumentNodeStore). Turns out that
-the DocumentNodeStore already has a heartbeat-like concept called leases. Those can be re-used for discovery, combined with
-an explicit materialization of the cluster view in the DocumentStore so that all instances agree and refer to the same
-view without the actual need for voting.
+Therefore it becomes necessary to be able to store heartbeats in a (low-level) location that provides higher consistency (than eventualness).
+Such a 'low-level location' is the DocumentStore of oak (which is an internal API of the DocumentNodeStore). Turns out that
+the DocumentNodeStore already has a heartbeat-like concept called leases. Those can be re-used for discovery to fulfill the same
+aspect as heartbeats do: indicate alive instances. This can further be combined with
+an explicit materialization of a "cluster view" in the DocumentStore so that all instances agree and refer to the same
+view without the actual need for voting (this is possible since the DocumentStore allows to do conditional updates).
 
 ### Jackrabbit Oak's discovery-lite
 
-All of the above mentioned features have been implemented in so-called 'discovery-lite'. Discovery-lite is a simplified
-version of discovery on the oak level. The only thing it provides is one descriptor: the 'discovery-lite descriptor'. 
+All of the above mentioned features have been implemented in so-called 'discovery-lite': Discovery-lite is a simplified
+version of discovery on the oak level. Other than the discovery API it only provides one thing, and that's the
+clusterview-json:
 
 #### 'oak.discoverylite.clusterview'