Consider this a call for contributions.
The latest changes to Felix' resolver adopt a generic
capability/requirement approach for resolving package export/import and
bundle provide/require constraints (with the goal of also using this
approach for host/fragment constraints too).
The benefit of this approach is that it provides a nice generic way off
adding and resolving additional types of constraints to the Felix
resolver. Another benefit is that this resolver implementation can be
shared with OBR, so the same resolver can be used for deployment as well
as runtime wiring.
The downside of this approach is that it relies heavy on LDAP
expressions and their evaluation, which tends to slow things down a bit.
To offset this slowdown, I have cut some corners making the
capabilities/requirements not as generic as I would like. I want this
approach to be as generic as possible, but this requires that we
optimize LDAP expression evaluation.
If anyone has experience in such areas and is willing to look into this
area for Felix, please let me know and I can explain more precisely what
we need. Overall, I think the work should be pretty localized, so it
should be an easy way to get involved for someone with experience in
this area.
Search your soul, you know you want to contribute! ;-)
-> richard
