[
https://issues.apache.org/jira/browse/SLING-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134136#comment-15134136
]
Bertrand Delacretaz commented on SLING-5274:
--------------------------------------------
I like the idea, had a quick look at the patch yesterday and it touches a lot
of things indeed. If we can find a cleaner/simpler way of doing the same thing
that would be better.
IIUC we want the RequestProgressTracker to be available early in the request
processing phase, maybe a non-Sling Filter is a good place to create it, and it
can be enhanced as the request progresses, with the Sling-specific objects.
> Include authentication in RequestProgressTracker
> ------------------------------------------------
>
> Key: SLING-5274
> URL: https://issues.apache.org/jira/browse/SLING-5274
> Project: Sling
> Issue Type: Improvement
> Components: Engine
> Reporter: Alexander Klimetschek
> Attachments: SLING-5274.patch
>
>
> The request progress tracker only starts with the sling filters, after the
> sling authentication ran through. Since authentication steps can be complex
> with multiple handlers (just like filters) and can have a major performance
> impact (custom auth handlers, slow resource resolver login) it would be very
> useful to include it with detailed information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
