And why is that? Shouldn't Wicket session filter such events and not consider them user interaction with the system?
Thank you both for the replies, and for the link also! Great help! Regards, Martin -----Original Message----- From: nino martinez wael [mailto:nino.martinez.w...@gmail.com] Sent: Tuesday, March 16, 2010 3:39 PM To: users@wicket.apache.org Subject: Re: Does AjaxSelfUpdatingBehavior simulate user actions and prevent session from expiration? yes. Ajax contacts the server. And on each request the timer are reset. So your ajax behavior are also functioning as a heartbeat or keepalive feature. 2010/3/16 Martin Asenov <mase...@velti.com> > Hello, everyone! > > In my webapp it looks like the session never expires, although I've set > timeout of 30 seconds. But I have a digital clock in my right lower corner > of the screen, that has an AjaxSelfUpdatingBehavior activated on it. Does it > simulate user actions, that may cause session not to expiry? > > Thank you, > Martin > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
