Yes, the datastore is the best place to store application state that doesn't change very frequently. Load the sate into a singleton on each instance. The problem with memcache is that you have no control over the eviction policy so your object could vanish.
On Dec 23, 5:23 am, Simon Knott <knott.si...@gmail.com> wrote: > Hi, > > Your best bet is the datastore, as this is probably the most reliable > shared service. You could potentially share state in a backend server, but > these too have a tendency to go down. > > Cheers, > Simon -- 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-java@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.
