You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2015/05/25 12:28:17 UTC
[jira] [Resolved] (FELIX-4860) Revisit HandlerRegistry
implementation
[ https://issues.apache.org/jira/browse/FELIX-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved FELIX-4860.
-------------------------------------
Resolution: Fixed
The servlet registry now uses a sorted data structure, with the potentially highest matching servlet first. As soon as a matching servlet is found, this can be used, no need to iterate over all servlets anymore.
With this I think we have improved the registry implementations; i guess there is always room for improvement, but we should create more specific issues once we hit sem.
> Revisit HandlerRegistry implementation
> --------------------------------------
>
> Key: FELIX-4860
> URL: https://issues.apache.org/jira/browse/FELIX-4860
> Project: Felix
> Issue Type: Sub-task
> Components: HTTP Service
> Reporter: Thomas Baier
> Assignee: Carsten Ziegeler
> Fix For: http.base-3.0.0
>
>
> The implementation of the HandlerRegistry class needs to be revisited. There is quite some code duplication between the code for the servlet handler registrations and error pages/filter registrations. Also it might be worth checking if the current division into a servlet handler registry and a per context registry is the best solution, also with FELIX-4779 in mind.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)