While getting the nodes from the iterator, lazily. I'm not sure that it can be reused, because it contains a lot of concerns that actually hold state.
But it is cheap to create so you can just encapsulate it in a function. Michael Am 02.07.2014 um 16:54 schrieb José Cornado <[email protected]>: > Hello! > > I am about to write a custom evaluator and I have a couple of questions: > > When does the evaluate(Path) happen? after calling traverse(Node) or after > getting the iterator? > > Can the traverse descriptions be reused once generated? Are there any > performance gains by reusing it other than the obvious reuse? > > Thanks a lot!! > > -- > You received this message because you are subscribed to the Google Groups > "Neo4j" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
