On Thu, Oct 20, 2011 at 8:35 AM, Alejandro Soto <smalejan...@gmail.com> wrote:
> Well, my system is like a ERP, what I want to do is basically: the user for > work with the system, first must to be authenticated, then the user can > works normally, then, if his session timed out, he need to relogin, that is > the reason because I need to control the sessions, but what the user was > doing before relogin, must be on hold, if the authentication is successful, > then the request of the user is committed. I think you would need to be a lot more precise about requirements, like what you mean by "what the user was doing before relogin". But generally, if you have some kind of transaction-in-progress when the session times out -- what's the question? You'll have to save the transaction state somewhere and re-associate it with the user's new session after s/he logs in again. The details could vary wildly according to your specific requirements :-) FWIW, -- Hassan Schroeder ------------------------ hassan.schroe...@gmail.com http://about.me/hassanschroeder twitter: @hassan --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
