I read with interest this conversation on a similar topic: http://groups.google.com/group/google-apps-apis/browse_thread/thread/3b191cc9dbefe937/5757612620d41390?lnk=gst&q=503+server+busy#5757612620d41390
One apparent difference with my case, however, is that I am using MailItemService.Batch() to upload 50 messages at a time. For each upload transaction, I examine the result feed for the status code of each entry. I see many instances where of the 50 entries in a feed, a third or maybe half of them are marked as "503" with the reason "server busy, try again later". The rest are as expected, code 201 "Created". Two important questions: 1) How do I prevent this from happening? My claim would be that in a batch feed the server itself should figure out how to queue/cache the entries in the feed so that it can handle them all, not just some of them. 2) Given that it's going to happen, how do I recover? I can imagine a technique whereby I find the entries in the result feed that have this problem, then match them (by batch id probably) with the original entries in the upload feed, then somehow submit them again (maybe 1- by-1? Or as a new batch feed?). This seems unreasonably complex, and also creates a ton more http traffic. Any suggestions? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Apps APIs" 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-apps-apis?hl=en -~----------~----~----~----~------~----~------~--~---
