[ https://issues.apache.org/jira/browse/SLING-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15525170#comment-15525170 ]
Carsten Ziegeler commented on SLING-6056: ----------------------------------------- [~egli] The split up can either be done in JcrResourceProvider#registerListener or we create a new class dealing with this and registerListener delegates to it. I think this depends on how complex the code gets. I'm not 100% sure if compaction of the listeners is already done in the resourceresolver implementation, e.g. if a listener registers at /foo/bar and another at /foo - we could consider only registering a single observer at /foo. Same, if a listener registers at /, we only need one observation listener. > 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: Resource Resolver 1.4.18 > Reporter: Stefan Egli > Assignee: Stefan Egli > Priority: Critical > Fix For: Resource Resolver 1.4.20 > > > 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)