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
Hi Mattias,
- GET / will return URIs for creating nodes and the reference node as
well as the index starting point.
Sounds sensible. What about using Atom feeds as the representation for a node
set and AtomPub for handling node creation etc?
- To have a browse:able representation in
2010/3/23 Jim Webber j...@webber.name
Hi Mattias,
- GET / will return URIs for creating nodes and the reference node as
well as the index starting point.
Sounds sensible. What about using Atom feeds as the representation for a
node set and AtomPub for handling node creation etc?
...@lists.neo4j.org] On
Behalf Of Jim Webber
Sent: Tuesday, March 23, 2010 11:39 AM
To: Neo user discussions
Subject: Re: [Neo] Continuing REST API development
Hi Mattias,
- GET / will return URIs for creating nodes and the reference node as
well as the index starting point.
Sounds sensible
I'm a fan of the AllegroGraph REST API, documented at
http://www.franz.com/agraph/support/documentation/current/new-http-server.html.
Take a look and see what's in there that you might provide, too.
Bill
___
Neo mailing list
User@lists.neo4j.org
5 matches
Mail list logo