[
https://issues.apache.org/jira/browse/SLING-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904934#action_12904934
]
Clemens Wyss commented on SLING-1603:
-------------------------------------
I guess Engine is implemented with the strategy pattern in mind? Strategies for
request processing?
If so, I would call the interface "Engine" more appropriately
"RequestProcessing", or "RequestProcessor" and hence EngineImpl would become
"SlingRequestProcessing" or "SlingRequestProcessor". #processRequest could then
become #process.
As this is only a naming-issue it's not really that important... :-)
> 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.
