I should re-phrase. What do you do if HRD fails now? The best you can do is log an error and hope for the best. Async doesn’t have to be fire and forget, it can be fire and check back as the last line of your code. You can actually use this as a way to make your apps more reliable. The last line of your code could be “If write failed URL FETCH AS POST DataToWrite” so that you could try the write again. Or you could add a task to fire later to add the data. Or you could log it. All of these would be better than Doing a write and having it fail syncrously (especially since if you are like my devs you don’t wrap your write in a Try. I don’t live in GAE Wonderland. I just spend time with my head in the Clouds, and Gae’s tend to rain on me the least. From: [email protected] [mailto:[email protected]] On Behalf Of André Pankraz Sent: Thursday, January 19, 2012 2:13 AM To: [email protected] Subject: Re: [google-appengine] Re: Put_Async Use It You always seem to be in a special GAE wonderland zone ;)
All operations can fail and...HDR or not...they fail sometimes. If a RDBMS would fail as often as HDR on writes I would throw it away. So my first question for such fire-and-forget async methods is: How do I handle errors: even in RDBMS environment. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/oIBLy58JKOUJ. 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. -- 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.
