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/11/11 21:40:39 UTC

[jira] Resolved: (SLING-1156) ResourceProviderEntry uses iterators rather than maps, this becomes expensive with apps with many servlets.

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

Ian Boston resolved SLING-1156.
-------------------------------

       Resolution: Fixed
    Fix Version/s: JCR Resource 2.0.8

Re-resolving this, SLING-1181 represents a bug in this code, and has been fixed under that issue.

> ResourceProviderEntry uses iterators rather than maps, this becomes expensive with apps with many servlets.
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: SLING-1156
>                 URL: https://issues.apache.org/jira/browse/SLING-1156
>             Project: Sling
>          Issue Type: Improvement
>          Components: JCR
>    Affects Versions: JCR Resource 2.0.6
>            Reporter: Ian Boston
>            Assignee: Ian Boston
>             Fix For: JCR Resource 2.0.8
>
>
> The ResourceProviderEntry uses iterators over many servlets, this is probably Ok for Resource resolution but when it comes to servlet resolution many are tested and this can be expensive especially if there are many servlets. IMHO, the class should be refactored to use trees of maps.
> This has been discussed on list, the intention is to create a contrib version to explore this further, not wanting to impact the active version in trunk.

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