A significant amount has been written about GWT, but a lot of it is cursory, API-wise. Not very much of it goes into implementation behavior. For example, the main interface into a GWT page is an EntryPoint. Each EntryPoint has a method called onModuleLoad().

So my first test is to test for validLogin. My EntryPoint.onModuleLoad makes an AsyncCallback to my GWT server-side service, which at this time, returns a False. [Cookie and Session support is going to be added at some point]

Then I present a Grid of widgets on the RootPanel that asks for username and password, with a Login button. This is then sent to the server in my doLogin() method, which does a static comparison for now, and returns TRUE or FALSE.

So the effort has paid off, and my test application allows me to submit login credentials, and get a main login page. When I use this from multiple browsers/sessions, I get the behavior I expect - the results of one session do not effect one another, by default.

Things are looking up for my first evolution of my main page.