svn commit: r1784741 - in /sling/site/trunk/content/documentation: bundles/apache-sling-eventing-and-job-handling.mdtext tutorials-how-tos/how-to-manage-events-in-sling.mdtext

[tm...@apache.org]

Author: tmaret
Date: Tue Feb 28 14:16:09 2017
New Revision: 1784741

URL: http://svn.apache.org/viewvc?rev=1784741&view=rev
Log:
SLING-6575 - Job delivery guarantee should be described as "at least once"

Modified:
    sling/site/trunk/content/documentation/bundles/apache-sling-eventing-and-job-handling.mdtext
    sling/site/trunk/content/documentation/tutorials-how-tos/how-to-manage-events-in-sling.mdtext

Modified: sling/site/trunk/content/documentation/bundles/apache-sling-eventing-and-job-handling.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/apache-sling-eventing-and-job-handling.mdtext?rev=1784741&r1=1784740&r2=1784741&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/bundles/apache-sling-eventing-and-job-handling.mdtext (original)
+++ sling/site/trunk/content/documentation/bundles/apache-sling-eventing-and-job-handling.mdtext Tue Feb 28 14:16:09 2017
@@ -23,7 +23,7 @@ In general, the eventing mechanism (OSGi
 On the other hand, there are use cases where the guarantee of processing is a must and usually this comes with the requirement of processing exactly once. Typical examples are sending notification emails (or sms), post processing of content (like thumbnail generation of images or documents), workflow steps etc.
 
 The Sling Event Support adds the notion of a job. A job is a special event that has to be processed exactly once. 
-To be precise, the processing guarantee is at most once. However, the time window for a single job where exactly 
+To be precise, the processing guarantee is at least once. However, the time window for a single job where exactly
 once can't be guaranteed is very small. It happens if the instance which processes a job crashes after the job 
 processing is finished but before this state is persisted. Therefore a job consumer should be prepared to process
 a job more than once. Of course, if there is no job consumer for a job, the job is never processed. However this

Modified: sling/site/trunk/content/documentation/tutorials-how-tos/how-to-manage-events-in-sling.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/tutorials-how-tos/how-to-manage-events-in-sling.mdtext?rev=1784741&r1=1784740&r2=1784741&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/tutorials-how-tos/how-to-manage-events-in-sling.mdtext (original)
+++ sling/site/trunk/content/documentation/tutorials-how-tos/how-to-manage-events-in-sling.mdtext Tue Feb 28 14:16:09 2017
@@ -1,6 +1,6 @@
 Title: How to Manage Job in Sling
 
-Apache Sling supports the execution of jobs with the guarantee of processing the job at most once. This can be seen as an extensions of the OSGi event admin, although jobs are not started or processed by OSGi events leveraging the OSGi event admin.
+Apache Sling supports the execution of jobs with the guarantee of processing the job at least once. This can be seen as an extensions of the OSGi event admin, although jobs are not started or processed by OSGi events leveraging the OSGi event admin.
 
 For more details please refer to the following resources: