[
https://issues.apache.org/jira/browse/SLING-6623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16014191#comment-16014191
]
ASF GitHub Bot commented on SLING-6623:
---------------------------------------
GitHub user npeltier opened a pull request:
https://github.com/apache/sling/pull/229
SLING-6623 allow async execution of pipes
- moved execution code to a central place, under plumber implementation,
- added status, and bufferization of the commits (async execution means
potentially long executions),
- added job registering & processing capabilities for plumber, based on a
configurable service user (will update documentation accordingly)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/npeltier/sling SLING-6623
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/sling/pull/229.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #229
----
commit e5b6158d6b297f32b523de9546bfb195c583ef11
Author: Nicolas Peltier <[email protected]>
Date: 2017-05-17T15:14:25Z
SLING-6623 allow async execution of pipes
- moved execution code to a central place, under plumber implementation,
- added status, and bufferization of the commits (async execution means
potentially long executions),
- added job registering & processing capabilities for plumber, based on a
configurable service user (will update documentation accordingly)
commit b13a3e85fb20ee487bd3f6efa1ea764ef6c0f546
Author: Nicolas Peltier <[email protected]>
Date: 2017-05-17T15:14:42Z
Merge branch 'trunk' of github.com:apache/sling into SLING-6623
----
> Add the possibility to execute sling pipes in a background thread
> -----------------------------------------------------------------
>
> Key: SLING-6623
> URL: https://issues.apache.org/jira/browse/SLING-6623
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
> Affects Versions: Pipes 0.0.10
> Reporter: Nicolas Peltier
>
> For now the only way to execute a pipe through HTTP is to wait for servlet's
> response to end.
> For very long pipes this is an issue (as well as for the fact all pending
> changes might impact memory), as well as it is error prone in case the same
> pipe is executed several times.
> this ticket is for adding a new execution mode, that write the running status
> of the pipe configuration, and makes the pipe executed in a separate thread
> than the servlet thread.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
