You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Nicolas Peltier (JIRA)" <ji...@apache.org> on 2018/06/08 13:45:00 UTC

[jira] [Assigned] (SLING-7718) Script engine should not be created for each contained or referenced path

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

Nicolas Peltier reassigned SLING-7718:
--------------------------------------

    Assignee: Nicolas Peltier

> Script engine should not be created for each contained or referenced path
> -------------------------------------------------------------------------
>
>                 Key: SLING-7718
>                 URL: https://issues.apache.org/jira/browse/SLING-7718
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: pipes 2.0.2
>            Reporter: Nicolas Peltier
>            Assignee: Nicolas Peltier
>            Priority: Major
>             Fix For: pipes 3.0.0
>
>
> A container or a reference pipe will systematically set bindings to sub pipes. For that reason, it's useless to create script engine instance (and pipebinding object in general).
> Moreover it drills down performance a lot when reference pipe or container pipe are used late in the pipe (i.e. are called a lot).
> This ticket is about changing the API to include bindings in the constructor of a pipe, if null, then it can be created



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)