On Mon, Oct 21, 2013 at 11:39 PM, Jukka Zitting <jukka.zitt...@gmail.com> wrote: > 3) The Observer mechanism allows a listener to look at repository > changes in variable granularity and frequency depending on application > needs and current repository load. Thus an Oak Observer can > potentially process orders of magnitude more changes than a JCR event > listener that needs to look at each individual changed item.
+1 I think in Sling case it would make sense for it to be implemented as an Observer. And I had a look at implementation of some of the listener implementations of [1] and I think they can be easily moved to Sling OSGi events Chetan Mehrotra [1] https://gist.github.com/chetanmeh/7081328/raw/listeners-list-filtered.txt
