Cool. While I'm not a complete REST purist, a cautionary suggestion: An HTTP "GET", in general, should never create or mutate anything. PUT and DELETE should/could, or an RPC-ish invocation via POST. And, since some browsers are fickle about supporting PUT/DELETE, a GET with a "hint" parameter such as &_method=put is a suitable workaround.
Ideally, the REST-ful API would support output (and input) in HTML, XML, and JSON. Rick -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Mattias Persson Sent: Tuesday, March 23, 2010 11:30 AM To: Neo4j user discussions Subject: [Neo] Continuing REST API development So, we finally got some time on our hands and will put some of that into continuing the development of the Neo4j REST API! Our focus at the moment will be: - GET / will return URIs for creating nodes and the reference node as well as the index starting point. - Indexing: Implement the functionality found in IndexService (the neo4j-index <http://components.neo4j.org/neo4j-index/> component) - To have a browse:able representation in addition to JSON, so that you can click your way through the graph - Batch operations: to define more than one operation to be performed in a single transaction Features to focus on after that: - Traverser support - Security - Transaction control operations (begin, commit, rollback) - Extensions - etc... Which features are you guys hungry for? Feedback would be very much appreciated. See more information at our wiki <http://wiki.neo4j.org/content/REST_API> -- Mattias Persson, [[email protected]] Neo Technology, www.neotechnology.com _______________________________________________ Neo mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user _______________________________________________ Neo mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
