You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Antonio Sanso (JIRA)" <ji...@apache.org> on 2015/02/19 14:00:14 UTC

[jira] [Closed] (SLING-4204) Better abstraction of internal Filter handling and add filter processing timing

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

Antonio Sanso closed SLING-4204.
--------------------------------

> Better abstraction of internal Filter handling and add filter processing timing
> -------------------------------------------------------------------------------
>
>                 Key: SLING-4204
>                 URL: https://issues.apache.org/jira/browse/SLING-4204
>             Project: Sling
>          Issue Type: Bug
>          Components: Engine
>    Affects Versions: Engine 2.3.10
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: Engine 2.4.0
>
>
> The Sling Engine web console configuration printer currently exposes all the Filter services that are used by the Sling engine.
> It would be great if we cold expose usage and timing information about those filters as well to see which filters attribute the most to request processing.
> At the same time internal filter handling can be improved to better abstract "holding" Filter services and leverage usage functionality such as said timing and tracking but also future requirements such as providing capabilities to not call filters unless some condition is met (e.g. only call a filter on certain resource types or paths)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)