[
https://issues.apache.org/jira/browse/SLING-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15244867#comment-15244867
]
Ian Boston commented on SLING-5645:
-----------------------------------
@Roy, I called it a JobSubsystem since that the name of the class that collects
together the JobManager and the registration of JobConsumers. Subsystem seemed
like the right word to describe that. It's certainly not an OSGi Subsystem or
anything to do with OSGi, other than being implemented to work inside Sling. I
don't really mind what its called. If Subsystem causes those that know about
OSGi Subsystems to get confused, then I can think of some other word. I guess
there are loads of features within Sling that fit the description of OSGi terms
without adhering strictly to the OSGi view of the world.
> Provide a Jobs API and implementation suitable for widely distributed job
> processing.
> -------------------------------------------------------------------------------------
>
> Key: SLING-5645
> URL: https://issues.apache.org/jira/browse/SLING-5645
> Project: Sling
> Issue Type: New Feature
> Reporter: Ian Boston
> Assignee: Ian Boston
>
> This issue is to track work on a proof of concept to create a Jobs API and
> implementation that will work in a distributed environment where the job
> submitters and job consumers are not necessarily in the same JVM or in the
> same Sling cluster.
> Work is being done in a branch at
> https://github.com/ieb/sling/tree/jobs_28/contrib/extensions/jobs
> Since the implementation needs supporting APIs/Capabilities not already
> present in Sling. There are some sub-tasks associated with this issue to
> address those.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
