Hi, We have received reports of extreme cases where a developer needs to wait up to 1 minute for an update. We know this is not ideal and until we make this more reliable, a solution is to retrieve the contact again and compare its ETag and/or updated time with the results of the update.
Cheers, Julian On Oct 21, 10:02 am, dflorey <[email protected]> wrote: > Hi Julian, > more info would be highly appreciated. Can you give us a hint how to > implement changing contact+photo in a reliable way? > My customers suffer from very strange side effects when enabling photo > sharing. > > Thanks, > Daniel > > On Oct 19, 2:14 pm, Zindus Development <[email protected]> wrote: > > > Julian (Google) wrote: > > > It is not possible to update the contact and the photo at the same > > > time, because updating a contact's photo causes a contact timestamp > > > change. In the other hand, there is a replication process behind the > > > scenes, this causes a delay after the update and because of this you > > > may need to wait a bit longer to be able to perform the second update. > > > By "wait a bit longer", can you suggest a reasonable threshold? 1s? 2s? > > 10s? > > > 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 -~----------~----~----~----~------~----~------~--~---
