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. Maarten On Sun, Apr 12, 2009 at 8:00 AM, Eelco Hillenius <eelco.hillen...@gmail.com> wrote: >> Both articles avoid the DiskPageStore problem by using the HttpSessionStore, >> however if you do a search through the mailing list archives for >> HttpSessionStore you'll find numerous references to problems in using it in >> the long term and especially in a real, production application, so I don't >> think that's a good long term solution, so my original question still >> stands. Is there an alternative or is Wicket perhaps not well suited for use >> in the App Engine. > > It's probably a good idea to have a specialized implementation of > ISessionStore for App Engine that uses whatever makes sense with App > Engine for medium term storage ('cause that's what it is... short term > storage is the current page, which is typically local memory, and > older pages are used for the duration of the session, and typically > just keeping the last few in memory suffices. > > Eelco > > --------------------------------------------------------------------- > 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
