Maybe you could use the AppEngine cache? You have the guarantee that objects in cache are replicated across instances. However you need to be extra careful in your locking mechanism as Object.wait() and Object.notify() obviously won't work. I guess some sort of polling can do it, if you don't need extra reactivity.
Afterthought: I'm wondering if cache object modification is seen immediately on other instance, or if there is some kind of "transactional mode" within a request, that makes the cache appear consistent for a whole request. You have to check that too, I guess. --Laurent On May 13, 7:34 pm, Samuel Erdtman <sam...@erdtman.se> wrote: > That is true, I just want to know that it is by design and not because I > have missed to do something. > > And the thing is that i can see the objects and that there is difference in > visibility after the first thread returns. does this mean that objects are > synchronized between data centers between request. > > I´ll see if i figure something out > > //Samuel -- 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.
