Alternatively, give session management to the server to handle using server technologies such as Spring or any other you are familiar with.
On Tue, May 17, 2011 at 12:44 PM, Jens <[email protected]> wrote: > You have to store some login information as cookie once the user has logged > in and your onModuleLoad / underlying controller has to check if that cookie > is present and if it is then check if these login information are still > valid (server request). If they are still valid you can show your > application instead of the login screen. > > -- J. > > > > > -- > 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. > -- Odeyemi 'Kayode O. http://www.sinati.com. t: @charyorde -- 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.
