Session isn't lost but session use is discouraged. You have memcache which is pretty fast in retrieval. Of course, every once a while even the memcache can be invalidated due to various reasons. While relying on memcache you need to be sure that in case the value returned is null query the datastore.
My app gets high traffic every hour. I do keep the user object in session and haven't come across any problems yet. -N On Jun 13, 6:33 am, Thomas <mylee...@gmail.com> wrote: > Session is cached in memcache and persisted to datastore. So when > loading request occurs it won't be lost if it is not expired. You can > view session (_ah_SESSION) data with datastore viewer. > > On 6月11日, 下午11時09分, Rahul <rahul.jun...@gmail.com> wrote: > > > > > No doubt if your application is low traffic you will definitely need > > memcache as session will be lost every minute when the jvm restarts > > and you need to reload everything and also session is highly > > discouraged due to various reasons. > > > Thanks, > > Rahul -- 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
