Depends on your definition of session and if you are using container managed security and if that is the case it can depend on your server. The default session manager for glassfish uses cookies, therefore as long as the user has cookies enabled they will be able to maintain a session as long as that cookie is alive. The problem is that IE and Firefox treat session cookies differently. FF will share session cookies across tabs while IE <= 7 will not. There are reports that IE8 will share session cookies across tabs. As we have seen with v8 of IE they are conforming to the rest of the browsers as long as they don't have to maintain bugs from IE6 due to compatibility(the box model bug comes to mind).
On Jul 16, 5:40 am, cooolcat <[email protected]> wrote: > Hey, > > I just started reading about GWT. It is really amazing and the > documentation is pretty good. But I still didn't find something useful > how GWT works with multiple tabs in the same browser. I guess, when I > call the same application in two different tabs, I will have two > different sessions. I would like to use the same session, expecially > when a user logged in. How can I do this? Can I check in a new tab if > a user already logged in, and how can I access this data? > > Any help is greatly appreciated. -- 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.
