I think I understand what you are saying. In this case, the app is a medical app and there are requirements that the app timeout after a period of inactivity (which is usually short: 15 to 30 minutes). When logging in, an event is triggered and the app state is "logged in". Currently, the timeout isn't implemented, but the app does check the session on each RPC call. When the session doesn't exist (is expired) the app state is "logged out". The way it works now is pretty good...except for linking within the app.
I'll need to think about what you suggest (setting a cookie after authentication) to figure out how to do it. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/dZUrrq2kqxMJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
