Hi Pranav, Including exception handling for downtime related errors is recommended. There are planned periods in which the datastore is in read-only mode for example. In those cases you can look for a CapabilityDisabledError (in Python). Displaying a human readable message sounds like a great idea.
Thank you, Jeff On Mon, Apr 20, 2009 at 10:09 AM, pran__ <[email protected]> wrote: > > Hi AppEngine team, > > First of all, i would like to say that you all did a wonderful job by > fixing the issue/downtime in appengine on Apr 20 2009, 06:30 AM PDT so > fast. This job is really appreciable. > > There were a few glitches tough. > > I would like to know about two things - > > 1. What was the cause of the issue? Sure, if the AppEngine team is > ready to share. If this was because of some issue in one or more of > the apps, is there something we (the developers) can do to prevent > it ? > > 2. What are the chances that this issue _might_ come up in future - > near or distant ? > > I am planning to add a layer to the datastore get/put that will > centrally manage all read/write operations in my app. if anything > fishy goes around, it will display some human readable error and > gracefully halt the application for time being. > > Thanks > Pranav Prakash > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
