Marcel Reutegger wrote:
Jukka Zitting wrote:
Marcel, what's the rationale behind the spec?
when you have events for properties like property_added,
property_removed and property_changed the node type filter only makes
sense for the parent node. it was then decided to use the term
'associated parent node' for each event and declare all filters
(absPath, isDeep, uuid and nodeTypeName) to apply to this associated
parent node, even for the node related events.
and in some cases it actually makes sense. imagine that you want to get
notifications when a node is added or removed from nt:folder nodes. Then
the API provides you with exactly that functionality. of course there
are other use cases such as the one mentioned by torgeir, which are not
properly supported by the API.
In which case the infamous advice on implementing acl based security
using listeners and acl caches doesn't work.
It doesn't seem possible at the moment to get notification whenever
nodes that have security information is created, updated or removed.
--
-Torgeir
