You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2016/01/26 14:37:39 UTC

[jira] [Commented] (SLING-5218) ResourceProviderAuthenticator must not hold stateless providers

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

Robert Munteanu commented on SLING-5218:
----------------------------------------

I'm not sure how to perform this change - the {{CombinedResourceProvider}} is built around {{StatefulResourceProvider}}s . I could build a {{StatelessStatefulResourceProvider}} but that sounds plain wrong ...

I'm detaching this from SLING-4750 since it is an internal implementation issue and can be followed up in a future release ; I'm eager to release a bundle with the new improvements.

[~cziegeler] - perhaps you have some ideas about to approach this, I'd be glad to hear them

> ResourceProviderAuthenticator must not hold stateless providers
> ---------------------------------------------------------------
>
>                 Key: SLING-5218
>                 URL: https://issues.apache.org/jira/browse/SLING-5218
>             Project: Sling
>          Issue Type: Improvement
>          Components: ResourceResolver
>            Reporter: Carsten Ziegeler
>             Fix For: Resource Resolver 1.3.0
>
>
> The ResourceProviderAuthenticator keeps currently a state provider object for each provider it uses. This is not necessary for all stateless providers (all servlet and bundle providers for example). We can reduce memory footprint by avoiding this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)