I've been thinking about your deal. Since the changes are happening concurrently, you could either sync the servlet threads up and talk across the servlets, which I have no experience and haven't tried servlet concurrency or keep track of the threads through a jdo class.
So here is what I would do in your case, I would setup another class to track the state of the object with a boolean flag of the existence of the object your persisting or deleting. This would act like a checkin/checkout that happens in svn per say. In either case, syncing the threads is the goal, at least thats my thought. I think this could help solve your collision problem. Brandon Donnelson http://gwt-examples.googlecode.com -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
