Hi, On Wed, Oct 23, 2013 at 4:01 PM, Dominik Süß <[email protected]> wrote: > ...This might not apply to the whole > tree, but does this really matter when the tree that needs to be watched > contains over 90% of the data?...
What's important is the frequency of observation events - if that 90% seldom changes, scaling won't be a problem. > ...If I got the problem right the overhead is created by the fact that an > event object is created and sent regardles if a consumer cares about it or > not. So it might be worth to add something that "asks" the listeners if > there is one that would consume this event... That's what I meant above: > ...A simple way of making our wide observation more specific is to > require users of our rebroadcast OSGi events to indicate more > specifically what they're interested in... There's various ways of doing that: service properties, calling a service to register your interest in certain types of events etc. -Bertrand
