Higher level observation servicesPage added by Bertrand DelacretazAnalyzing how we use observation in our Sling-based apps shows a number of recurring patterns, described in this page. Using JCR observation directly or Sling OSGi events does not make a big difference in the final results, but the implementations are very different. The commit hooks provided by http://jackrabbit.apache.org/oak/ provide yet another way of observing content changes, which might be more efficient or scalable in some cases. Being able to express these common observation patterns as higher-level services, if we can do that, would allow for switching the underlying implementation seamlessly, and would also help promote best practices in how we use events, by minimizing the amount of code to write at the application level.
Change Notification Preferences
View Online
|
Add Comment
|
- [CONF] Apache Sling > Higher level observation services confluence
- [CONF] Apache Sling > Higher level observation services confluence
- [CONF] Apache Sling > Higher level observation services confluence
- [CONF] Apache Sling > Higher level observation services confluence
- [CONF] Apache Sling > Higher level observation services confluence
- [CONF] Apache Sling > Higher level observation services confluence
- [CONF] Apache Sling > Higher level observation services confluence
- [CONF] Apache Sling > Higher level observation services confluence
- [CONF] Apache Sling > Higher level observation services confluence
- [CONF] Apache Sling > Higher level observation services confluence
- [CONF] Apache Sling > Higher level observation services confluence
