Why are you throwing CapabilityDisabledErrors on memcache writes? Couldn't you silently fail? There's no guarantee that stuff in memcache will still be in memcache, so I don't see why it needs to error on failures. Even the API reference says it returns False on errors - nothing about it preventing a page from rendering.
memcache is commonly used, and there's no warning in the docs that it can throw page-breaking errors. By throwing CapabilityDisabled, you've wrecked a lot of pages that could otherwise render right now. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
