You could consider using a more functional approach. The user usually has model classes and basic functions already, so why write model classes for vertices and edges? Instead, write awesome algorithms that take function arguments such as getNeighbors: (node) => node array, getDistance: (node, node) => number, etc.
At least, that was my thinking when I wrote async-bfs - https://npmjs.org/package/async-bfs On Saturday, June 15, 2013 8:44:19 PM UTC+2, Kaique da silva wrote: > > I'm writing a Graph engine using node... this is the draft: > > https://github.com/kaiquewdev/Graph > > Please, give me feedback to improve the concept. > > Thanks! > -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" 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/groups/opt_out.
