[
https://issues.apache.org/jira/browse/SLING-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17084749#comment-17084749
]
Julian Sedding edited comment on SLING-9365 at 4/16/20, 10:47 AM:
------------------------------------------------------------------
[~karlpauls] I've pushed some code I had to the whiteboard, maybe it's helpful:
[https://github.com/apache/sling-whiteboard/tree/feature/sling-resource-graft]
On second thought, I'm not sure if ResourceDecorator will work for you. I have
a feeling that they are only called during request processing. But that could
be fixed, I guess.
was (Author: jsedding):
I've pushed some code I had to the whiteboard, maybe it's helpful:
[https://github.com/apache/sling-whiteboard/tree/feature/sling-resource-graft]
On second thought, I'm not sure if ResourceDecorator will work for you. I have
a feeling that they are only called during request processing. But that could
be fixed, I guess.
> 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)
