You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2017/05/24 07:23:04 UTC

[jira] [Resolved] (SLING-6623) Add the possibility to execute sling pipes in a background thread

     [ https://issues.apache.org/jira/browse/SLING-6623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Munteanu resolved SLING-6623.
------------------------------------
    Resolution: Fixed

Applied in [r1796004|https://svn.apache.org/r1796004], thanks for the patch!

> 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
>            Assignee: Robert Munteanu
>             Fix For: Pipes 0.0.12
>
>
> 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)