-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Alejandro,
On 10/20/2011 11:35 AM, Alejandro Soto 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. > > Any advice will be welcome. Keep as much information in a <form> on the page as you can for long, possibly interruptable workflows. When you submit that <form>, if the session is dead, after re-authentication, the form submission will be replayed and the workflow can continue. We do this exact thing in pretty much all of our flows: each <form> submission has enough information to resume the flow even after a session expiration. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6giqIACgkQ9CaO5/Lv0PChagCePRzdvasTHVV4UEoq1psdWzEG auwAoJwIGB+WoVvDlZcpCPatIk4RHYxS =4Y80 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
