[SLING-5201] Improve resource provider resolving

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: API 2.11.0, Resource Resolver 1.4.0
• Component/s: ResourceResolver
• Assignee: Carsten Ziegeler
• Reporter: Carsten Ziegeler
• Created: 27/Oct/15 09:33
• Updated: 08/Feb/16 22:11
• Resolved: 29/Oct/15 13:44

Description

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)