Hi, On 8/29/07, Stefan Guggisberg <[EMAIL PROTECTED]> wrote: > On 8/28/07, Jukka Zitting <[EMAIL PROTECTED]> wrote: > > A thought just crossed my mind... As mentioned in another thread a few > > days ago, we could make NodeImpl to load the underlying node states > > only on demand as long as we have just the node ID, parent ID, and > > name of the node available. This way we could "delay" the exception to > > a method like getProperty() that is allowed to throw appropriate > > exceptions. > > > > Besides, such a solution would most likely give a nice speedup to > > clients that just want to get the names or paths of nodes that match a > > query... > > sounds interesting. however, with our current Node/PropertyState model > you would still need to load NodeState's along an item's path in order > to resolve its path since names are stored in the parent state.
True. Intermediate nodes higher up on the content tree would usually be in the cache, so I think the performance benefits would still be pretty good. BR, Jukka Zitting
