[
https://issues.apache.org/jira/browse/SLING-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15243557#comment-15243557
]
Roy Teeuwen commented on SLING-5645:
------------------------------------
Hey Ian,
Maybe a strange question, but why is it called JobSubsystem? When thinking of
subsystems I immediately think about OSGi Subsystems, while when looking at the
implementation, it does not have any link to this.
OSGI Subsystem references:
https://osgi.org/javadoc/r5/enterprise/org/osgi/service/subsystem/Subsystem.html
http://aries.apache.org/modules/subsystems.html
Greets,
Roy
> 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)
