I can only say that I've been using Wicket on GAE for awhile and it seems to work pretty well, with some extra effort. For now, I'm just using HttpSessionStore. I asked in the GAE forums about the performance there and they said session storage made heavy use of the MemCache to keep performance strong. It is possible that Wicket can store very LARGE objects in the SessionStore, but that may be an indication of poor page detaching. After making that improvement, my session data rarely exceeds 100K.
I may try out a pure MemCache version based on the link you provided, see if I can get it lower and less dependent on the session. The only other serialization issues I've noticed deal with changing model objects across requests - I instead am forced to replace components on occasion, instead of replacing model objects. That's a hack right now and I'll look into it later. Don't know anything about JBoss. Jake -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/GAE-serialization-issues-tp2068427p2075571.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
