Hi, That's a nice idea! But wouldn't it be confusing that one can get a Node object through the nextNode() method which does not exist in the repository anymore?
Would this proposal also make the Node.getNodes(String pattern) method less expensive? As I gather now all infrastructure for the child nodes is created but might not be used if the child nodes name does not fit the pattern. Best regards, Martijn -- Martijn Hendriks <GX> creative online development B.V. t: 024 - 3888 261 f: 024 - 3888 621 e: [EMAIL PROTECTED] Wijchenseweg 111 6538 SW Nijmegen http://www.gx.nl/ > -----Original Message----- > From: Marcel Reutegger [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 29, 2007 10:14 AM > To: [email protected] > Subject: Re: Database connections & queries > > Jukka Zitting 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... > > +1, sounds like a very interesting idea. > > regards > marcel >
