On Wed, Apr 17, 2013 at 8:36 AM, Jukka Zitting <[email protected]> wrote: > ...My thinking here is that the best approach for most use cases will be > to use a commit hook to consolidate the low level changes to less > granular application events that can then be processed in the > background using JCR observation, OSGi events, a generic message queue > system, or directly by a polling thread in the client application....
>From my JCR user's point of view, I like that - I often find myself merging JCR events to get a more meaningful view of actual changes and keep load low, at the application level. Having hooks for that in Oak sounds great, but the full event stream probably needs to optionally be available, at least in a "JCR compliant" mode. -Bertrand
