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. -Clint -- 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.
