Good news: http://groups.google.com/group/google-appengine-java/msg/f50bbb131dc524c1
<quote> "HttpSessions will work out of the box if you enable them in your appengine-web.xml. We do not guarantee that all requests for the same session go to the same JVM, but persistence of sessions is managed behind the scenes with the datastore and memcache. You are, of course, free to use the memcache and/or datastore API's directly if you want more control. " </quote> Maarten On Sun, Apr 12, 2009 at 4:18 PM, Adriano dos Santos Fernandes <adrian...@uol.com.br> wrote: > Maarten Bosteels wrote: >> >> But AFAIK GAE doesn't use/guarantee sticky sessions, so I am afraid >> you can't rely on local memory. >> >> "App Engine uses multiple web servers to run your application, and >> automatically adjusts the number of servers it is using to handle >> requests reliably. A given request may be routed to any server, and it >> may not be the same server that handled a previous request from the >> same user." >> >> http://code.google.com/appengine/docs/java/runtime.html#Requests_and_Servlets >> >> It would be interesting to test the performance of an ISessionStore >> backed by the App Engine datastore. > > FYI, I've put a app. with a static variable counter (just a static, not in > session). And since two days there, the counter is maintained. > > So I guess they solution uses something like Terracotta. BTW, they web > server is Jetty. > > > Adriano > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
