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/04/27 09:16:38 UTC
[jira] [Comment Edited] (FELIX-4866) Improve service registry
[ https://issues.apache.org/jira/browse/FELIX-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14513643#comment-14513643 ]
Carsten Ziegeler edited comment on FELIX-4866 at 4/27/15 7:15 AM:
------------------------------------------------------------------
I've committed a first updated implementation in rev 1676200.
Major changes are:
- moved all hook related registrations into separate class
- instead of a complicated for/wait/notify cycle in register/unregisterService a wait/notify mechanism is used, the state is directly hold in the registration object, removing the need for an additional map
- where possible, collections are now non blocking
The c't still passes with these changes
was (Author: cziegeler):
I've committed a first updated implementation in rev 1676200.
Major changes are:
- moved all hook related registrations into separate class
- instead of a complicated for/wait/notify cycle in register/unregisterService a wait/notify mechanism is used, the state is directly hold in the registration object, removing the need for an additional map
- where possible, collections are now non blocking
> Improve service registry
> ------------------------
>
> Key: FELIX-4866
> URL: https://issues.apache.org/jira/browse/FELIX-4866
> Project: Felix
> Issue Type: Improvement
> Components: Framework
> Affects Versions: framework-5.0.0
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: framework-5.2.0
>
>
> The current service registry is currently not using any of the Java 5 concurrent data structures. Using those could improve the implementation, the readibility of the code and potentially the performance of the service registry.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)