The two HTTP requests are not guaranteed to execute in the same VM, regardless of session ID, so you should definitely NOT rely on thread interaction. The session object is updated in real time, and of course memcache is a great tool for sharing short lived state, as long as you can tolerate failures.
However, it sounds to me like you should really explore the Channel API to accomplish your goal: https://developers.google.com/appengine/docs/java/channel/overview On Thursday, May 10, 2012 9:21:02 AM UTC-4, Davide Montesin wrote: > > Hi, > > I like to develop a Rich User Interface. To obtain this on user > interaction I need two thread: one for action processing, > and one for incrementally update the client side (html). > I generate two http requests from the client. The two request must > communicate. > The "update" request must exchange data with the "action" request. Both > request have the same > session id. > > Can I use the session for exchanging data between two thread? Or can be > that at the same time > exists more than one node/jvm that is elaborating the same session id? If > yes, data in session > is synchronized in realtime? > > What about synchronizing the two request. Can I use the Thread.wait/notify > or no because > request for the same session can be on different nodes? > > Must I poll the session from a thread to discover if the other thread has > written new information? > > Exist another way, i.e. memcache, to obtain this in google app engine. > > Thanks in advance for any help! > > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/Y_5YcyXW9Z0J. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
