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 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 E
yes i awared memcache and do this. beside memcache is there any other
way? i though is memcache has tendency to go down out of service as
well.
--
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 go
