[google-appengine] Re: Datastore timeouts and retries.

2009-01-10 Thread djidjadji

Be aware that there are times that memcache is disabled. At certain
maintenance activities memcache.get() always returns None and
memcache.set() has no effect.
And memcache will be cleared when maintenance is over and normal
behavior has returned.

Your application must be able to deal with this situation.

2009/1/10 David Wilson d...@botanicus.net:
   * Somehow use memcache as an alternative.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~--~~~~--~~--~--~---



[google-appengine] Re: Datastore timeouts and retries.

2009-01-10 Thread David Wilson

2009/1/10 djidjadji djidja...@gmail.com:

 Be aware that there are times that memcache is disabled. At certain
 maintenance activities memcache.get() always returns None and
 memcache.set() has no effect.
 And memcache will be cleared when maintenance is over and normal
 behavior has returned.

 Your application must be able to deal with this situation.

Indeed. My point was that this isn't really a workable alternative to
simply retrying the Datastore request.

Thanks,


David.


 2009/1/10 David Wilson d...@botanicus.net:
   * Somehow use memcache as an alternative.

 




-- 
It is better to be wrong than to be vague.
  — Freeman Dyson

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~--~~~~--~~--~--~---