You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2015/10/27 10:44:27 UTC

[jira] [Updated] (SLING-5201) Improve resource provider resolving

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

Carsten Ziegeler updated SLING-5201:
------------------------------------
    Fix Version/s: API 2.10.0

> Improve resource provider resolving
> -----------------------------------
>
>                 Key: SLING-5201
>                 URL: https://issues.apache.org/jira/browse/SLING-5201
>             Project: Sling
>          Issue Type: Improvement
>          Components: ResourceResolver
>            Reporter: Carsten Ziegeler
>             Fix For: API 2.10.0, Resource Resolver 1.2.8
>
>
> With the new implementation, whenever the best matching resource provider for a path is searched, the implementation calls:
> CombinedResourceProvider#getMatchingProviders(path) which returns a list and then the first element from the list is fetched (through the head method).
> I think we could and should avoid creating the unnecessary intermediate list object, and simply return the most matching provider (which is the last one matching)



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