[
https://issues.apache.org/jira/browse/SLING-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli updated SLING-6056:
-------------------------------
Description:
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]
was: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.
> 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
> 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)
