[ 
https://issues.apache.org/jira/browse/SLING-5994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15436446#comment-15436446
 ] 

Stefan Egli commented on SLING-5994:
------------------------------------

Was thinking of a 'wildcard / catch-any' parameter (eg {{/apps/*}}) which could 
be used if you are interested if anything changed there, but if multiple 
changes occur you don't necessarily want to be informed about each one 
individually, but just one 'bulk' event without the details. If something like 
this would be a frequent pattern then we could _collapse_ events in oak perhaps.

> Move from Deprecated EventHandler to new ResourceChangeListener API
> -------------------------------------------------------------------
>
>                 Key: SLING-5994
>                 URL: https://issues.apache.org/jira/browse/SLING-5994
>             Project: Sling
>          Issue Type: Task
>          Components: API
>            Reporter: Hanish Bansal
>
> This issue serves as the container for the issues for migrating all 
> implementations of EventHandler to new Resource Observation API in Sling Code.
> The new API that listens to the resource events is : 
> https://github.com/apache/sling/blob/trunk/bundles/api/src/main/java/org/apache/sling/api/resource/observation/ResourceChangeListener.java
> API for the Resource Change Events : 
> https://github.com/apache/sling/blob/trunk/bundles/api/src/main/java/org/apache/sling/api/resource/observation/ResourceChange.java



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to