> 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.
Does jackrabbit really make a request per next() call on the children iterator or does it optimize and fetches all children (as long as the number is reasonable low) when retrieving the iterator? > > 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 > > > > >
