I'm seeing this behavior too, and it seems to be new. It is indeed problematic. Anyone from Google care to comment? Or ever better, to announce a fix? :-)
Thanks, Charlie On Jun 13, 4:46 pm, tazz_ben <[email protected]> wrote: > I think this issue is new (I don't think it use to do this), but if it > isn't and you working on it, I apologize. There seems to be a delay > from the time that an item is updated and when it will appear in the > API feed (I've been trying to figurate out the exact amount, but it > seems to be less than five minutes). This is problematic given that > that when you pull based updated-min you then store the value of > "updated" value returned with the results, it (the updated value) is > NOT delayed. So to sum up: > > * The items in the feed can be delayed > * but the value of updated is not delayed > > The result of this combination, is that it is possible to miss items > if they are updated/created right before a pull. My current work > around to this is to subtract five minutes from the last update before > placing it in updated-min. > > Ideally, if the data is delayed in the API feed, the updated should > contain when the feed was updated NOT what the current time on the > server actually is. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
