Observation usage patternsPage comment added by Felix MeschbergerJust a minor detail on impact: OSGi events are dispatched fully asynchronous and thus don't block event processing in the repository.
In reply to a comment by Bertrand Delacretaz:
If by "this" you mean the tentative API, then agreed, I'll remove it. The interesting thing is that a number of the patterns mentioned here might not need observation at all, a form of slow polling would work for most of them and be more scalable. As you say, the Sling JcrResourceListener makes it easy to listen to specific events, but to support that it has to blindly relay a lot of JCR events to the OSGi event queue, which might also hinder scalability. I'll run some tests with Oak to measure what the actual impact is.
Change Notification Preferences
View Online
|
|
- [CONF] Apache Sling > Observation usage patterns confluence
- [CONF] Apache Sling > Observation usage patterns confluence
