You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Joerg Hoh (Jira)" <ji...@apache.org> on 2023/05/26 07:32:00 UTC

[jira] [Closed] (SLING-11876) Avoid creating response wrapper for every include

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

Joerg Hoh closed SLING-11876.
-----------------------------

> Avoid creating response wrapper for every include
> -------------------------------------------------
>
>                 Key: SLING-11876
>                 URL: https://issues.apache.org/jira/browse/SLING-11876
>             Project: Sling
>          Issue Type: Improvement
>          Components: Engine
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>            Priority: Major
>             Fix For: Engine 2.15.0
>
>
> When the sling request dispatcher is used, it currently creates a response wrapper for every include, in some cases even two.
> For many sling requests there are sometimes hundreds of not thousands of includes during a request. We could improve debugging by not creating a wrapper with every include.
> This might also have a minor performance improvement.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)