Re: [Neo4j] Graph algos in REST

I'm not convinced I like the way this works: POST /node/123/paths {to: http://localhost:/node/456;, algorithm: shortestPath, max depth: 100} Isn't the intention to retrieve the shortest path? If so I'd prefer: GET

Re: [Neo4j] Graph algos in REST

Until Neo4j supports operations on distributed graphs, couldn't we assume the destination is another node in the same graph and clean that up to: GET /node/123/paths?to=456algorithm=shortestPathmaxDepth=100 Also, I believe Neo4j only has a stable of reindeer. Would one of them do? /Andreas On

Re: [Neo4j] Graph algos in REST

2010/9/17 Jim Webber j...@webber.name I'm not convinced I like the way this works: POST /node/123/paths {to: http://localhost:/node/456;, algorithm: shortestPath, max depth: 100} Isn't the intention to retrieve the shortest path? If so I'd prefer: GET