[
https://issues.apache.org/jira/browse/SLING-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15529285#comment-15529285
]
Carsten Ziegeler commented on SLING-6056:
-----------------------------------------
Ok, so we can add a new reportChanges method to ObservationReporter instead
which also takes the configuration as an argument.
Sorry, but I'm still not sure what you're trying to achieve.
Let's assume we have three listeners, one for /libs and two for /content
without any further restrictions.
The ObservationReporter will report two configurations, one for /libs and one
for /content.
The jcr resource module will register two observers based on that and today
call ObservationReporter.reportChanges for any change under /libs or /content.
The resource resolver implementation does then the dispatching to the correct
set of the three listeners. How do you want to change this picture?
> 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.4.20
>
> 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
(v6.3.4#6332)
