In this way, you need to get hold of the server generated session id in client first time and use it to check whether session id stored is null or not. Just wanted to check, whether it would be a best practice solution?
On Jun 21, 12:15 pm, Nikola Markovic <[email protected]> wrote: > 1. Keep your session id on the client aswell. That way you know if you're > logged in, or not, on the client side. User can type in an URL and if the > user isn't logged in, you can just switch to a login activity. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. 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.
