Hi, On Wed, Oct 23, 2013 at 11:30 AM, Dominik Süß <[email protected]> wrote: > ...I have at least 2 cases in mind where the paths cannot be > determined at deployment time...
We studied observation usage patterns [1] earlier this year on a few Sling-based apps and it turns out that a lot of that can be done without observation, which might help scalability. So I'd say let's concentrate on Sling itself, and provide a way to be more specific in how observation is used, for the cases where that matters. And/or replace observation with other mechanisms where appropriate. 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. This can be enabled by a configuration switch, so that small apps that don't care require no changes, and larger systems that require scalability can turn on that switch and have to do a bit of work to provide more details. Large scalable systems require work anyway, so this is not too much to ask for IMO. -Bertrand [1] https://cwiki.apache.org/confluence/display/SLING/Observation+usage+patterns
