The memcache is volatile without a well defined contract for expiration, so it alone is not sufficient to support session behavior. A memcached entity is more like a SoftReference in contract. Well a globally shared SoftReference with, presumably, some cross JVM network serialization overhead (that last part being a guess).
On Dec 28, 2009 6:59 PM, "Paul Jacobs" <paul.r.jac...@gmail.com> wrote: HttpSession seems to be using the datastore by default in my app. Can it be made to use memcache? I have not used memcache yet, so I hope this isn't a daft question... -- 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<google-appengine-java%2bunsubscr...@googlegroups.com> . For more options, visit this group at http://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 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.
