On 16.7.14 4:12 , Michael Dürig wrote:
- Path exclusion would allow certain paths to be excluded from sending events. This is helpful if you want to listen to say /content but not to /content/foo. Relieving event handlers from handling such exclusions will lower client code complexity and increase performance.
I created JCR-3797 and OAK-1978 to track this.
- User data exclusions would allow for excluding events with certain user data. This could be useful if a session wants to bulk write some data without the respective event handlers being fired. That session would just need to set the user data to the same value as specified in the exclusion filter.
No much enthusiasm for this one, also from my side... such a feature has the issue that it would no work across cluster nodes as session related information does not come across cluster nodes.
Michael
