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

["Carsten Ziegeler (Jira)" <ji...@apache.org>]

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

Carsten Ziegeler resolved SLING-11876.
--------------------------------------
      Assignee: Carsten Ziegeler
    Resolution: Fixed

Merged all different response wrappers into the already existing SlingHttpResponseWrapperImpl and using a data object on RequestData (same for the request)
https://github.com/apache/sling-org-apache-sling-engine/commit/09da9ad1ef560c451d37baaf80a0c919244621da

> 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)