Kyle, While you *may* be able to do that, the general GWT way would be to have your urls look more like this:
mysite.com/myapp.html#/acmeHairSalon mysite.com/myapp.html#/genericDogCollars And you can easily access the tokens via the History class (the getToken method). HTH, Chad On Mar 23, 8:24 pm, Kyle Baley <[email protected]> wrote: > Not sure I understand. I plan to filter data on the server side of > things. But I don't know how to configure GWT to allow me to navigate > to specific client for the entire app. > > For example, Acme Hair Salon would navigate to mysite.com/ > acmeHairSalon/myapp.html and Generic Dog Collars would navigate to > mysite.com/genericDogCollars/myapp.html. Both URLs should map to the > same instance of the application but in it, I'd check the URL to see > which company was being used and filter all the data in it > accordingly. I know how to do the filtering and can probably figure > out how to check the URL for a company token. But I don't know how to > configure GWT and/or GAE to use a single instance of the application > for multiple (generic) URLs that aren't pre-defined. It sounds to me > like something that should be done in web.xml but again, I don't know > how. > > On Mar 23, 1:01 pm, "[email protected]" <[email protected]> wrote: > > > > > So you can just built the ui once and always include it in the login > > page for which ever client as the server should be where you filter/ > > prevent access to data that's not for the current client. > > > On Mar 22, 10:41 am, Kyle Baley <[email protected]> wrote: > > > > I'm new to GWT and the Java world having been in the .NET space for > > > about 10 years. Our application will be a multi-tenant one (at least, > > > to the degree that I understand the definition). We'd like customers > > > to be able to navigate towww.mysite.com/customerName, then log in > > > from there. I think I have a handle on how to manage this from the GAE > > > datastore side but am wondering how to manage this URL mapping in > > > web.xml for GWT. > > > > Also, would like to get some opinions on how to manage the > > > authentication once it's set up. Here's how I see it working: > > > - User navigates towww.mysite.com/customerName > > > - System retrieves company data and stores in session and displays > > > login page > > > - User logs in. System authenticates user > > > - For all RPC calls, system verifies user is logged in *and* checks > > > that the URL matches the company info in the session > > > > Basically, I want to guard against a user logging into one client > > > site, then navigating to another. > > > > Thanks > > > Kyle -- 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.
