We've had similar design issues in the past. The easiest and stablest (sp?) solution was to create a session concept in your database and do everything there. We were unable to make the session object on various web containers behave consistently....but your mileage may vary.
On Oct 23, 10:03 am, lalit <[EMAIL PROTECTED]> wrote: > Hi, > > I have three GWT application[ A, B and C] . All these three > application having login screen. My requirment is that if User already > logged in Application 'A' then he should be able to move on > application B and C without making a login for B and C. > > Suppose after login for A, A application having two click buttton to > move on B or C. > > Please could you help to find out the solution. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
