a) After authenticating the user, make a RPC call to the server to get the permissions map for the user. On the server side, get the userid from the session rather than the request parameter. b) On the client side, use the permissions map to figure out if a particular link can be shown or not. c) Be aware that client side disabling/enabling buttons is only usability and not security. In each your RPC Services you must check if the logged in user has the necessary permissions to perform the operation. Again, it is a matter of using the session object to see if the user is authorized.
-sri On Aug 30, 4:08 am, mathesmond <[email protected]> wrote: > Hi, > > I would like to enable/disable buttons in my application based on user > permissioning , this should happen at the time of application startup. > can you please provide me some pointers as to how this can be > achievedi > > Cheers --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
