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

Carsten Ziegeler commented on SLING-6056:
-----------------------------------------

I've added a new method to the api as discussed above - the old method is still 
in place as it can be used if the implementation is just using a single 
mechanism like registering a single JCR 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: 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
(v6.3.4#6332)

Reply via email to