Hi! The guys who wrote the REST component are offline at the moment, so I'll just chime in here for now.
You are right that the current REST API won't allow you to control transactions: it wraps each request in a transaction. There's basically two strategies, either you keep a transaction open spanning multiple requests, or you bundle the operations together somehow and send them in a single request. It would be interesting to hear some different views on this topic from the community - what would be useful to you? /anders Javier de la Rosa wrote: > Hi all, > > I think there's no way to perform a transaction through Neo4j REST > Server. It would be great if we could emulate this behaviour using the > header Keep-Alive, some session variable or some persistence issue. > A good option can be the next (I'm guessing Neo4j isn't able to manage > several transactions simultaniously, but I don't really know): > Create transaction > POST /transaction > > Example using curl > $ curl -H Accept:application/json -X POST > http://localhost:9999/transaction > > Response > 201: OK, a transaction was created > 409: Transaction already in progress > > Since that moment, whatever you do will be under the transaction. When > you finish the transaction. the DELETE verb has to be invoked over > /transaction: > DELETE /transaction > > Example using curl > $ curl -X DELETE http://localhost:9999/transaction > > Response > 204: OK, no content returned > 404: Transaction not found > > What do you think about this? Is it too many complicated? Is it possible? > > Best regards. > > > _______________________________________________ Neo mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
