Hi, You can assume all Neo4j APIs are thread safe. If something is not thread safe it will be explicitly stated in the javadocs.
If you keep all state that has to be shared between threads in the graph and all other state thread local you don't have to perform any external (or extra) synchronization at all. If you have state that is not graph data and needs to be shared between threads keep that in separate synchronization blocks without invoking any mutating operations on the graph. Regards, Johan On Sat, Jun 4, 2011 at 7:22 PM, McKinley <mckinley1...@gmail.com> wrote: > I'm working with Neo4j as an EmbeddedGraphDatabase on a web server. It is > not Servlets, but the same multi threaded concerns apply. Is this > http://wiki.neo4j.org/content/Servlets_with_Neo4j still the most current > example of dealing with multi threaded concerns? > > I see many mentions on avoiding unnecessary uses of synchronized in the > current documentation at http://docs.neo4j.org/. Can those warnings in the > documentation have a simple multi threaded example included too? > > Thanks, > > McKinley _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
