As stated, so far the whole discussion is very theoretical - apart from the point that right now the jcr listener does a read for each and every changed node to get the resource type. This could definitely be improved with Oak as Oak is doing a content diff and therefore it should be possible to send this information down to the jcr listener. This would speed up things dramatically. But without concrete numbers and performance information, all of this sounds like premature optimization. Reinventing the wheel just slightly different without any way to proof whether it helps just doesn't sound right to me. We need to have a look at the whole system - it doesn't help if we talk about fixing one part of it for such scenarios while completely neglecting other parts. Therefore, (I know I repeat myself) I'm really looking forward to numbers showing the bottlenecks.
Thanks Carsten -- Carsten Ziegeler cziege...@apache.org
