sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Sedding (Jira)" <j...@apache.org>
Subject [jira] [Commented] (SLING-9365) Optimize servlet to resource provider servlet mounter
Date Thu, 16 Apr 2020 09:42:00 GMT

    [ https://issues.apache.org/jira/browse/SLING-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17084711#comment-17084711
] 

Julian Sedding commented on SLING-9365:
---------------------------------------

[~karlpauls] oh sorry for the noise. Obviously I didn't read the ticket carefully enough.
Glad that the ResourceDecorator idea may be of help!

> 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)

Mime
View raw message