Like Peter said, the credit for the PHP client should be on Todd and on Al
that have built the bulk of it. I'm über-up for continuing work on the
refactoring, but am crazy short on time in the next few months.
Todd - I just talked to Mattias, and the changes you wrote are already
available in the latest version of neo4j-rest :)
See http://components.neo4j.org/neo4j-rest/#Finding_a_path_between_two_nodes
I got a bit ahead of myself in my fork of the php client, and went ahead and
changed the name to neo4j.php. I'd like to formally propose that as a name
for the project. The current name, Neo4J-REST-PHP-API-client, doesn't
quite roll of the tongue. That would go with the names of other clients like
neo4j.rb and neo4j.py.
Come to think of it, there might be confusion there though. Both the other
projects are wrappers around the embedded graph database, not REST clients.
Perhaps neo4j-client.php?
/Jake
On Tue, Oct 19, 2010 at 12:51 PM, Todd Chaffee t...@mikamai.com wrote:
Hi Peter,
I'll see if I can get me, Jake, and Olle all on board to finish the
refactoring and merge back with the original branch. Functionally the PHP
client works and is ready. We'd like to add unit tests and better organize
the code.
How about the REST api? Any word on whether the path algos will be
included
in an upcoming release? That and traversals are probably the most useful
parts of the PHP client.
Thanks,
Todd
--
MIKAMAI | Making Media Social
http://mikamai.com
+447868260229
___
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user
--
Jacob Hansson
Phone: +46 (0) 763503395
Twitter: @jakewins
___
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user
