Carsten Ziegeler commented on SLING-6056:

I had an offline discussion with [~egli] and now I understand why the change of 
the api is required:
There might be listeners with overlapping configurations, if reportChanges is 
called without the used ObserverConfiguration then the implementation of the 
reporter is called several times for overlapping events and the reporter will 
deliver them to the listeners, which means that a listener might get the event 
twice (or more often based on the overlapping)

> achieve 1:1 mapping between observation and resource change listener
> --------------------------------------------------------------------
>                 Key: SLING-6056
>                 URL: https://issues.apache.org/jira/browse/SLING-6056
>             Project: Sling
>          Issue Type: Task
>          Components: ResourceResolver
>    Affects Versions: JCR Resource 2.8.0, API 2.14.2, Resource Resolver 1.4.18
>            Reporter: Stefan Egli
>            Assignee: Stefan Egli
>            Priority: Critical
>             Fix For: JCR Resource 2.8.2, API 2.15.0, Resource Resolver 1.5.0
>         Attachments: SLING-6056.patch
> At the moment it seems there is a 1:n mapping between 1 OakResourceListener 
> (and 1 BasicObservationReporter) and n ResourceChangeListeners. The idea 
> however is to get rid of such a bottleneck and have a 1:1 mapping (that might 
> or might not be in the BasicObservationReporter, that I don't know). We 
> should implement such a 1:1 mapping.
> See [thread on dev list|http://sling.markmail.org/thread/uwhda777psgklwo6]

This message was sent by Atlassian JIRA

Reply via email to