Marko, On Tue, May 27, 2008 at 8:15 PM, Marko A. Rodriguez <[EMAIL PROTECTED]> wrote: > While you can design grammars for moving through a multi-relational > network in complex ways, the limitation is that it is not Turing complete > and thus, there will ultimately be a computation that can not be done that > the developer will want to do. It is the opinion of myself that the > Traverser framework of Neo should be an interface only and it is up to the > developer to make the functional mapping from current vertex to next > vertex. E.g. --- sometimes you may want to teleport to some non-adjacent > vertex, sometimes if two traverses are at the same vertex they should > influence each other in some way, sometimes the path of one traverser > should determine the path of another, sometimes a traverser should have a > probabilistic choice, sometimes the traverser should have a decaying > energy value, etc. There are algorithms out there (and near to general > user needs) that the current Neo Traverser model can not efficiently > solve. IMHO you should file an issue on this (Traverser framework as interfaces and SPI for multiple traverser implementations, the current one being one of them)
/peter -- GTalk: neubauer.peter Skype peter.neubauer ICQ 18762544 GTalk neubauer.peter Phone +46704 106975 LinkedIn http://www.linkedin.com/in/neubauer http://www.neo4j.org - New Energy for Data - the Graph Database. http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software. http://www.qi4j.org - New Energy for Java - Domain Driven Development. _______________________________________________ Neo mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
