[
https://issues.apache.org/jira/browse/SLING-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17083348#comment-17083348
]
Karl Pauls commented on SLING-9365:
-----------------------------------
[~diru], yes, that would be one of the benefits.
[~cziegeler], yeah, it would have some limitations and downsides (as search
would be hard and at a minimum slow, events would be problematic, and copy/move
wouldn't work). I think your point is interesting to not have them at all -
I'll try to POC that as well and see if that causes other issues.
> Optimize servlet to resource provider servlet mounter
> -----------------------------------------------------
>
> Key: SLING-9365
> URL: https://issues.apache.org/jira/browse/SLING-9365
> Project: Sling
> Issue Type: Improvement
> Components: Scripting
> Affects Versions: Servlets Resolver 2.6.4
> Reporter: Karl Pauls
> Assignee: Karl Pauls
> Priority: Major
> Fix For: Servlets Resolver 2.6.6
>
>
> The current ServletMounter creates a resource provider for each registered
> servlet. That works fine for a given amount of servlets but can become
> problematic for a high number of servlets as it means that on the one hand,
> the number of services is doubled and on the other hand, a lot of
> notifications are send out as well as a lot of computation has to be done by
> the resource resolver.
> As an optional remedy for these kinds of scenarios, we should allow to
> configure the mounter to instead provide a single resource provider that has
> manages the servlets internally.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
