Details
-
Task
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
JCR Resource 2.8.0, API 2.14.2, Resource Resolver 1.4.18
-
None
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.
Attachments
Attachments
Issue Links
- blocks
-
SLING-5994 Move from EventHandler to new ResourceChangeListener API
- Resolved
- is blocked by
-
JCR-4032 Add jmx EventListenerMBean.getToString() for clearer consolidated listener stats
- Closed
-
OAK-4855 Expose actual listener.toString in consolidated listener mbean
- Closed
- is related to
-
OAK-4581 Persistent local journal for more reliable event generation
- Open
-
SLING-6070 Reduce temporary storage required in JcrResourceListener, call reportChanges earlier
- Closed