Probably not the right place to debate UI patterns, but some of the most successful web sites let you do all you can without requiring you to sign in or register. They ease you into the sign up process. Throwing a login or privilege exception is a great way to implement that pattern. GWT allows you to easily exceptions from the server to the client, so it is easy to implement. But if there isn't something you don't want an anonymous user to see, you can always disable those till you have authentication. And when a user first navigates to the site, check a return on whether the session is authenticated to enable/disable UI components.
Another side to this is you always want especially privilege exceptions to be thrown just to stop hackers from playing. The UI might not let you edit another users record, but some hacker may play with with the JS in firebug and do it anyway. So you need the privilege exceptions. -- 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/-/VHZwOGNpUXBlWHdK. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
