[
https://issues.apache.org/jira/browse/SLING-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904976#action_12904976
]
Felix Meschberger commented on SLING-1603:
------------------------------------------
Thanks for the feedback.
@Celemens: I in fact considered the name RequestProcessor, But in the end I
went for Engine because it is the main driver in the Sling "Engine" of the
Sling "Engine" module. But then, I would also be fine with RequestProcessor.
@Bertrand: Probably right. Or, combined with Clemens' comment:
SlingRequestProcessor.
Re: SLING-1213: The main refactoring of the filter handling is due to splitting
tasks of the SlingMainServlet. As a consequence a disctinct patch for
SLING-1213 based on the attached patch would just add more values to the
FilterChainType enum and a fews ifs here and there. That's why I thouhgt it
would be ok to mix. But if you think it is important I can split this up.
> SlingServlet service
> --------------------
>
> Key: SLING-1603
> URL: https://issues.apache.org/jira/browse/SLING-1603
> Project: Sling
> Issue Type: Improvement
> Components: Engine
> Affects Versions: Engine 2.0.6
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Priority: Minor
> Attachments: SLING-1603-fmeschbe.patch, SLING-1603.patch,
> SLING-1603.patch
>
>
> For SLING-550 I need to call the SlingMainServlet outside of the web
> container's request/response cycle.
> I'll attach a patch that introduces a new SlingServlet interface that
> SlingMainServlet implements.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
