Hi Julian - > Does the Zindus Thunderbird Addon retry inserts when an error occurs? > This would explain the 404 and the entry been inserted.
The contact is present on the GET that immediately follows the 404 POST. The pattern is repeated a number of times over a period of some minutes (a few successful POSTs then one of these successful 404 POSTs) so while a network connectivity issue is of course possible, it would be a wierd pattern of network failure. Also, if the 404 was being returned from some intervening point in the network, it would still be left to explain why the contact is present on the subsequent GET. I'm not trying to press the issue here - am happy to leave it unexplained if you are. Re: operation rate: when an error occurs the addon only retries after some (long) time, unless the user manually initiates another sync, which is what happened in this case. By way of a thought around better pinpointing this class of issue in future, is there any way of distinguishing a 404 that comes from Google vs from some other origin? eg. some HTTP header? Leni. Julian (Google) wrote: > Hi Leni, > > I understand it is difficult to look for the problem if it comes from > a user's report. It is really odd to get a 404 and have the entry > inserted, my best guess is a network connection problem. Did you get > more reports on this issue? > > Does the Zindus Thunderbird Addon retry inserts when an error occurs? > This would explain the 404 and the entry been inserted. > > By high operation rate, I mean the number of queries/inserts per > second. If the number of errors increases with a high load it is > advice to do an exponential back-off on retries. > > -Julian > > > > > > > > > On Mar 6, 9:17 pm, Zindus Development <[email protected]> wrote: >> Julian (Google) wrote: >>> Is this problem still happening or was it just a temporary issue? >> It's a problem report from a user of the zindus thunderbird addon, so >> you can understand why this is a difficult question to answer. >> >>> Were you using Batch or did you have a high operation rate? >> Not using batch in this case. If you let me kow what what you mean by >> "high" operation rate I'll answer that :-) >> >> If you'd care to speculate on what the issue might be I'd be interested. >> To the extent that the API can be used in a way that minimizes >> failures, so much the better. >> >> Leni. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Contacts API" 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-contacts-api?hl=en -~----------~----~----~----~------~----~------~--~---
