Re: [Neo4j] no remote thread-safe API

The issue there is that your client requests each have their own transaction so there. If you want to execution multiple requests transactionally in one block you should use the new batch-rest API. http://docs.neo4j.org/chunked/milestone/rest-api-batch-ops.html Cheers Michael Am 30.06.2011 um

Re: [Neo4j] no remote thread-safe API

Hi Aliabbas, > is it true that in neo4j there is no remote thread-safe API. No. That is a false assertion. The REST API is thread safe since it wraps the same thread-safe code as the Java APIs. There can still be *contention* but there is always thread safety (and ACIDity). Jim ___

[Neo4j] no remote thread-safe API

is it true that in neo4j there is no remote thread-safe API. This means that when making a multi-threaded solution you run into problems when updating relationships between nodes. Under stress you are likely to want to update a relationship while another thread has a lock and as such you run into p