> > If I used only one browser session, I invoked Main entrypoint on two > separate Firefox tabs, > will both instances of Main be contending to write to "static public > Main mainref"? > No. Each tab is a different context altogether. They will not interfere with each other at all.
Or does a static variable in GWT is actually a global to all frames within > the same root frame of an instance of Main? > Static variables in GWT do not translate to globals in javascript. Please advice: > - the DOM mapping of frames by GWT > - the behaviour of static variables in a GWT module. > When you include a GWT module, it creates a hidden iframe behind the scenes. The id of this iframe is your module name. The generated javascript code is scoped to this iframe. Say you have a html page which has another iframe. If the main page and iframe include the same gwt module, they will still be scoped differently. Methods and Variables in one module will not interfere with the other module. Both will retain their individual state. As to how history would be maintained - I don't know. Its going to be completely messy. Since both google and open id login/outs require uri and callbacks, I cannot > possibly eliminate the frame so that Main and User could refer > to each other in any honky-dory fashion. > I think I now understand what you are trying to do. OpenId requires the user to be redirected to a provider (like google) for authentication; but you don't want the user to leave your site. So you want to send the user to the provider in an iframe. Take a look at the gwt-exporter <http://code.google.com/p/gwt-exporter/>project. It allows you to export your GWT methods as standard javascript methods. In your case, you can export your refresh() method as a JS method, and then use your iframe to call it using standard JS techniques. Or, you could just redirect the user to the OP, let the user authenticate himself over there, and then let the OP redirect to your website when everything is done. This is a simpler flow for the user, and a lot simpler for the developer. This is the standard way it is done - see how its implemented on stackoverflow.com. --Sri On 7 April 2010 15:58, Blessed Geek <[email protected]> wrote: > I thought, I did not need to expose the innards of my app. > The namedframe housed in the dialogbox is actually a google or open id > login. > > Since both google and open id login/outs require uri and callbacks, I > cannot possibly eliminate the frame so that Main and User could refer > to each other in any honky-dory fashion. > > -- > 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]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- 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.
