Carsten Ziegeler commented on SLING-6163:

I think we have three options:
- we leave it as is 
- For files we find a way that Oak can already send us a changed event for the 
parent file node of jcr:content
- instead of reading, we simply always send two events: changed for the 
jcr:content node and for it's parent, regardless whether this is a file
Maybe there are more/better options?

> Improve observation of files in JCR
> -----------------------------------
>                 Key: SLING-6163
>                 URL: https://issues.apache.org/jira/browse/SLING-6163
>             Project: Sling
>          Issue Type: Improvement
>          Components: JCR
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: JCR Resource 2.9.0
> Currently, if a jcr:content node is modified, and an observation event is 
> sent out, the jcr listener reads the parent node to find out if this 
> jcr:content is a sub node of a file. If so, it reports a change on the file 
> node.
> This is required for all listeners interested in changes in files, as they 
> usually listen for a file node change, but not for the sub node /jcr:content 
> - which doesn't exist with other resource providers anyway
> The problem is that this read is done for every change of a jcr:content node, 
> regardless whether this is a file. And if several props change on such a 
> node, it is read over and over again

This message was sent by Atlassian JIRA

Reply via email to