[
https://issues.apache.org/jira/browse/SLING-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976105#comment-14976105
]
Carsten Ziegeler commented on SLING-5201:
-----------------------------------------
I'm not 100% sure but I think the list is also used to create the
ResolveContext - most of the info, especially the chain of parent resolvers is
"static", therefore most it can be calculated once. getResolveParameters is the
only exception.
I think this hints at a flaw in the api design, we should separate the parts
which don't change in the ResolveContext from the parts which are different for
each resolution
> 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)
