[
https://issues.apache.org/jira/browse/SLING-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13654637#comment-13654637
]
Carsten Ziegeler commented on SLING-2829:
-----------------------------------------
In addition, the capabilities of an instance are distributed in a cluster with
a property provider, providing the property
""org.apache.sling.event.jobs.consumer.topics""
> Add API for starting a job and service interface for executing a job
> --------------------------------------------------------------------
>
> Key: SLING-2829
> URL: https://issues.apache.org/jira/browse/SLING-2829
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: Extensions Event 3.1.4
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Extensions Event 3.2.0
>
>
> Currently it requires sending a special job event to the event admin to
> create a job. Once the event is sent, the sender has no knowledge whether
> this job has been received by the job implementation or not.
> Executing a job is currently done by sending an event to the OSGi event admin
> and waiting for a handler to process this job. Again, this adds a lot of
> overhead and uncertainty. Especially as the job handling does not know
> upfront whether a processor for a job exists or not.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
