You need an RPC call for authentication, and at least one more for
every other type of call you want the user to perform. If you're
worried about whether or not the user is still authenticated, use
session variables and session cookies... Please don't ever make a
boolean MayIDoSomething() AND a Object DoSomething() RPC call... Just
make the "DoSomething()", and check session variables for the user to
see if they're allowed to do what they ask.
You can make Exceptions serializable so you can send them back down
the wire to tell the user what went wrong {Not allowed is much
different than "session expired"}...
And, now that I actually read what you wanted to hear, I see that
answer is nothing like what you needed at all.
It's all design choice. You can put all your RPC in a single set of
Task,TaskAsync and TaskImpl classes, or you can make multiple classes
and deploy at multiple urls. My guess is you would get better
tracking / logging using different urls for different RPCs;, GWT
doesn't get confused if you put one hundred RPCs in a single
monolithic class, but you might!
Personally, I'd put authentication / user tracking in one place, and
service calls in another. That way, the next time you want a
different app with different service calls, you can reuse your
authentication.
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
-~----------~----~----~----~------~----~------~--~---
