You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Ian Boston (JIRA)" <ji...@apache.org> on 2009/06/22 13:58:07 UTC

[jira] Updated: (SLING-1017) JCR Resource Resolver 2 generates the same immutable array of JcrResourceTypeProviders on each request.

     [ https://issues.apache.org/jira/browse/SLING-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ian Boston updated SLING-1017:
------------------------------

    Summary: JCR Resource Resolver 2 generates the same immutable array of JcrResourceTypeProviders on each request.  (was: JCR Resource Resolver 2 )

> JCR Resource Resolver 2 generates the same immutable array of JcrResourceTypeProviders on each request.
> -------------------------------------------------------------------------------------------------------
>
>                 Key: SLING-1017
>                 URL: https://issues.apache.org/jira/browse/SLING-1017
>             Project: Sling
>          Issue Type: Bug
>          Components: JCR Resource
>    Affects Versions: JCR Resource 2.0.6
>            Reporter: Ian Boston
>         Attachments: SLING-1017.path
>
>
> THe JCR Resource Resolver creates 1 array of JcrResourceTypeProviders per request, even if there has been no change to the array. The Array is immutable once created and so it should really be created on change not on request.
> The creation of this array alos synchronizes all request, which is probably not great for scalability.
> patch to follow

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.