On Mon, 2002-08-12 at 17:46, Marcel Maatkamp wrote: > > Or add a method 'List MMObjectBuilder::getNodes(List objectnumbers)', > > where the getNodes will return MMObjectNodes of the type(subtype) of the > > builder specified. > > The MMObjectBuilder can decide how to handle the request on the builder > > for the nodes. When a node is mentioned in the list and not in the > > builder, i think it is valid to throw an exception. > Which I prefer to let it call the getNode-method, which in effect is the same as >what I > propose above. You could argue that this would now be cachable, which would only > marginally speedup frequently reloaded pages, on the expence of having > another builder-cache which should be maintained by its nodes. If we would have a MMObjectBuilder.getNodes(List nodenumbers), the nodes that are already inside the cache(nodeCache.containsKey(new Integer(number))) can be retrieved this way. The othernodes _could_ be retrieved by an search. This would mean that with just one more query, the node-cache can be filled. This way it can be garanteed that the getRelatedNodes() will produce 2 queries max, and will use the cache as much as possible (unless the returnCorrectObjectBuilderTypes variable is turned into true in MMObjectBuilder, which could result into 1 more query than your proposed sollution).
Should we put it into cvs, so that everyone can have a look at it?(if it is really needed, we need to take some action..) -- Eduard Witteveen Systeem Ontwikkelaar NOS Internet, Gateway C Kamer 107 +31(0)356772910 http://www.omroep.nl/ Sed quis custodiet ipsos custodes? : The sixth Satire from Juvenal
