[
https://issues.apache.org/jira/browse/SLING-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794554#comment-13794554
]
Stefan Seifert commented on SLING-3173:
---------------------------------------
we should not bother on this for the first/upcoming release of the new job API,
but in the medium term it would be good to have more flexibility here - either
by adding more out of the box queues or allowing to extend them.
our example of a "time window queue" is not easily done using the scheduling
features because this would put the burden of the time queue to the job
consumer implementations. the jobs and the cliend code that posts the jobs
should not need to now about this special queue type, it should be added only
by configuration like the other queue types.
> Job Engine: Support custome queue implementations
> -------------------------------------------------
>
> Key: SLING-3173
> URL: https://issues.apache.org/jira/browse/SLING-3173
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
> Reporter: Stefan Seifert
> Priority: Minor
>
> follow-up from SLING-3028
> Q: is it possible to add own queue implementations? does not seem so, its
> using a hardcoded enum. in our own job implementation we have e.g. a "time
> window queue" think, which queues up jobs and executes them only in defined
> time windows where low user traffic is expected on the instance.
> A: Own queue implementations: these are not possible at all. For your use
> case of a time window queue, you maybe could use the scheduled jobs? If you
> think it's worth exploring this, please create a separate issue.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
