On Saturday, March 24, 2012 4:10:45 AM UTC+1, Clint wrote: > > In my application, I have 2 types of users: normal users and abnormal > users (kidding). Actually when one role is logged in, there are sections of > the codebase that I don't want the other role to have any way to know about. > > What is the best way to lock down serving up the code that I need to be > locked down? > > In the past, I had 2 modules with 2 separate entry points, and protected > the second based on the URL access, but that forces the users that use both > sections of the app to have to redownload the common Core, GWT, and > CssResources. Those common pieces of code won't be shared between the > separate modules. >
Why wasn't the second app a super-set of the first one? Using a JSP (or whatever) as your HTML host page, you could then selectively (depending on the user) send the first or second app (generate the script tag for the appropriate *.nocache.js). If you really don't want the code to be downloaded by non-authorized users, that's how I'd do it. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/kwJ9Ga2yuS8J. 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.
