what you are about to implement is something bigger than a simplified logic of admin/not-admin user, but rather privileged/unprivileged. Therefore in many cases like using CAPTCHA (robot defense), that's a matter of your taste as a web-designer to call the server for serialized UI elements, or merely ask it for an approval to actually render missing UI, which you already got on client since his very first http-request (or one, that sucks an appropriate DOM structure for this A&P particularly). It's really all about statically keeping a session on server side until it expires and mapping it to some privileges (regular user, accountant, manager, sysadmin). To make things easier and have your servlets as *smart* content providers, build your business logic over some modern MVC framework.
-- 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/-/4-Q41jSa0f0J. 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.
