Re: [Neo4j] Multiple users on a embedded graphdb

2011-05-11 Thread Michael Hunger
No problem at all. As tx are bound to the executing thread. And the singleton graph-db instance is the way to go. Good Luck with your efforts Michael Am 11.05.2011 um 17:04 schrieb John Doran: Thanks Micheal, Good points, I have 3 weeks to finish up(along with a mountain of other things

Re: [Neo4j] Multiple users on a embedded graphdb

2011-05-09 Thread John Doran
Hi Jim, Thanks for the reply, I haven't delved into the server aspect of neo4j(I'll leave that until I finish up college). I'll have to refresh my threading knowledge, you reckon each time users want to interact with the db to create a thread and this would stop any exceptions relating to not

Re: [Neo4j] Multiple users on a embedded graphdb

2011-05-09 Thread Marko Rodriguez
Hey, You can have multiple threads talking to the same DB reference. You can not create multiple graph database services over the same directory. Thus, final graph = new GraphDatabaseService('/tmp/test') for(int i=0;i10;i++) { new Thread { public void run() { // do something

Re: [Neo4j] Multiple users on a embedded graphdb

2011-05-09 Thread Thomas Baum
hi john, imho the gwt is just a webapp. so i'm a bit confused why talking about threads in a j2ee env? if i understand you right you want to share one neo4j instance between different gwt apps(services). i would propose creating a context-listener, on application startup the