Some questions: 1) Did you run the server trace on your code to see what was slow?
2) One idea -- rather than calling UserServiceFactory.getUserService() every time in the servlet -- why not hang onto that in the Servlet (say, by doing that once in the constructor) and using it over and over (so long as the Servlet is long-lived, all subsequent calls will be much faster). 3) What have you tried, and what are you seeing? Cheers Mike On May 25, 5:18 am, Ice13ill <[email protected]> wrote: > I'm building an app that uses Google account auth. > The application also uses a custom persistent entity (UserProfile) for > users that are registered (so basically there are functionalities that > can be used for free and others by registering). > At the beginning, the app was simple, so at every request the user was > checked by calling .getUserService().getCurrentUser() (including at > first login obviously). But it seams that a call to that method can > sometimes take about 3-5 seconds and also, clearly it is not he best > way. > So I need some advice implementing the session part, using what is > described in the appengine documentation (session-enable + memcache + > etc) . It does'n seem hard, but I know that some hints&tips could help > me at the beginning. > Thanks. > > -- > 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 > athttp://groups.google.com/group/google-appengine-java?hl=en. -- 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.
