On 13.01.11 08:25, "Markus Joschko" <[email protected]> wrote: >I thought more in the direction of node traversal. Instead of loading >just one node and checking ACLs I have to load the parent node and >three childnodes to get a complete view. I have no idea how node >retrieval is implemented in jackrabbit but given there is a database >behind I fear that I have four db requests (parent+3 children) reads >instead of one to create my view.
This depends on the persistence manager. The bundle DB persistence manager will do that (one bundle per node), but if you use e.g. the embedded Derby or H2 persistence managers, you don't have network latency. Also, the nodes are cached in Jackrabbit in-memory, so if you have repeated read-only access to those nodes, there will be no need to fetch them from the persistence manager again. But you touch a good point: generally it is good to have a higher property per node ratio - something like 5-10 properties per node. With 4 nodes per request however, it should still be fine! Regards, Alex -- Alexander Klimetschek Developer // Adobe (Day) // Berlin - Basel
