[
https://issues.apache.org/jira/browse/FELIX-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16010101#comment-16010101
]
Carsten Ziegeler commented on FELIX-5221:
-----------------------------------------
Another possibility - and improvement - would be to get services like the
servlets, filters etc lazy when they are requested for the first time. This
would also make all unused whiteboard services never get activated (assuming
they use something like DS)
> Reduce locking when service are registered/unregistered
> -------------------------------------------------------
>
> Key: FELIX-5221
> URL: https://issues.apache.org/jira/browse/FELIX-5221
> Project: Felix
> Issue Type: Improvement
> Components: HTTP Service
> Reporter: Carsten Ziegeler
>
> Currently when a new service is added/removed/modified through the
> whiteboard, the whole process is done within one global lock, forcing all
> operations to be done in sequence.
> In addition, this code calls out to the service registry, which we should
> avoid.
> I think we can solve this by treating SCH registration differently from all
> other services and use something like a change count for the SCH
> registrations: when a new whiteboard service is added, it's processed with
> the current set of SCHs. Once it's done it compares the current change count
> to the one from when the registration started. If it's different, it updates
> the registration. This is repeated until the count is equal.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
