i will probably do that. i was contemplating between that approach and
sending the data from the client.
Thanks.
regards
Ashwin
On Tuesday 09 August 2011 04:12 PM, Mark wrote:
If you're authenticated then can't you just send your query and let
the server-side code figure out who is making the call?
On Aug 9, 1:35 am, Ashwin Desikan<[email protected]> wrote:
Folks,
What is the best way to store user information ( i require only the
user-id) in the client? I have to pass user-id along with my queries to
the server to filter responses for the logged-in user. I fetch
user-information using the UserServiceLocator as part of the application
login. I am currently making a gwt-request every time to fetch the
currentUser in the following manner
requests.userServiceRequest().getCurrentUser().fire(new
Receiver<GaeUser>() {
@Override
public void onSuccess(GaeUser user) {
userId = user.getEmail();
userName = user.getNickname();
}
});
With the above approach, I have to run my subsequent queries to fetch
user-related data onSuccess of the above operation. Is there a better
approach to store the logged-in user-id on the client, instead of making
a server call every time?
Any suggestions?
regards
Ashwin
--
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.
