How can I distinguish this DeadlineExceededError from the one that happens when your whole request is about to run out of time? I guess that I can see how long the request has been running, and if less than (say) 25 seconds, then it must be the temporary one, otherwise the rather more serious one.
Essentially, when I get the download error, I make a request to another web server and ask it to fetch the web page, and then post the result back to my app (asynchronously). I'm not sure that I want to do this (and generate the javascript to trigger the retry) if I'm about to run out the clock on the whole request. In this case, it is probably better to just retry the whole request and hope that it doesn't happen again. Maybe I should just trigger the retry mechanism in any case when I get DeadlineExceededError and hope it doesn't turn consistent. Thanks Philip On Apr 27, 6:30 am, Nick Johnson <[email protected]> wrote: > Hi Philip, > > A DeadlineExceededError is a generic error that indicates the RPC call > took too long (which implies that the site also didn't respond in > time). It's safe to handle it in the same manner you would handle a > DownloadError. > > -Nick Johnson --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
