thanks, having proper setup of clustering with session replication should be the correct way to go in long term
but for this stage, we are restricted to solve the problem at application level our application can afford to have "ajax session expire" if we restart our server(s) occasionally, but we want to handle that "ajax session expire" exception gracefully at client side can we "hack" the wicket codes (java/js) that can intercept the ajax session expiration? any class/pointer that i should look at? Erik van Oosten wrote: > > ywtsang wrote: >> because we discovered that we can't preserve the session if the server >> is restarted >> > Ah, I understand. Well, you could if you use a servlet container that > support this, or if you use Terracotta. > > Regards, > Erik. > > -- > Erik van Oosten > http://day-to-day-stuff.blogspot.com/ > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/client-side-handling-of-ajax-request-session-expiration-tp16743324p16767350.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]
