Hi everyone, what is a reasonable setup/realization for enabling "restoring" RPCs after a session timeout, server restart/disconnect and re-login?
Take the following scenario: - GWT application on standard Tomcat - container managed authentication via login.jsp (simply redirects to GWT html upon authentication) Now if a timeout occurs or the application server is restarted or the client was disconnect long enough for the session to expire and the application then issues a RPC it will fail, since the session is lost and a new login is required. A copy/paste, "hello world" login.jsp would simply redirect to the starting point GWT application html. This causes the application to be simply started again (restarted) and all previous internal state like in memory cache is lost. So are the RPCs issued as the session was already expired. Related posts in this group: http://groups.google.com/group/google-web-toolkit/browse_thread/thread/91f74a1b6293b89b/ae90dee11b49408e http://groups.google.com/group/google-web-toolkit/browse_thread/thread/7d6b8dd5175e0e47/d999a1dd0e50287b We already realized the heart beat pattern (periodical ping) to prevent the session from timing out however such cases like a server restart or client workstation temporarily losing network connection still form scenarios where RPCs and hence data might get lost. Regards -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
