Perhaps you'd better use your own userssion with one pojo class On Mon, Mar 1, 2010 at 9:49 AM, opok <[email protected]> wrote:
> I currently use Google Account to authenticate and get the current > user like this: > > UserService userAction = UserServiceFactory.getUserService(); > User user = userAction.getCurrentUser(); > > I notice that the user service does not need HttpServletRequest to get > the current context, is that reliable? > > What about my customer use another google id to login in another page > of my app? Would the current user change when the customer returned to > the first page to make some other requests ? > > In the past, I always use Session to storage user information to id > current user, it looks like Google's user service can provide the same > functionality, so I can abandon the session for that kind of usage, is > that correct? > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to > [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-appengine-java%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- dream or truth -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-appengine-java?hl=en.
