> I'd rather make two completely distinct modules (i.e. two apps), and > load the appropriate one (the appropriate *.nocache.js) depending on > the user. > > This solves the admin/normal user problem, but is complicated for a more fine grained problem.
> In any case, there's no need to filter out the app JS code > (*.cache.html) from the users (it will hurt caching too), as long as > your server denies requests to *data* (and services, or whatever you > call them) to unauthorized users (i.e. even if the operational user > finds out how to launch the sales module, it won't have access to the > invoices data, making it useless). > > I am already implementing this aproach on server-side, I was looking for a way to reduce how much code will be visible to the client-side of my application. Thanks for the attention. -- André Moraes Analista de Desenvolvimento de Sistemas [email protected] http://andredevchannel.blogspot.com/ -- 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.
