Hi Leni, I have not been able to reproduce the problem, I am using:
"http://www.google.com/m8/feeds/contacts/user\%40domain.com/full? showdeleted=true&updated-min=2009-01-11T21:40:58.000Z"; and "http://www.google.com/m8/feeds/contacts/user\%40domain.com/thin? showdeleted=true&updated-min=2009-01-11T21:40:58.000Z"; and I always get the <gd:deleted /> for the deleted contacts. Do you have any other information that could help reproduce it? Is the issue showing up in different users? Thanks, Julian On Jan 26, 3:49 am, Zindus Development <[email protected]> wrote: > I'm still seeing problem reports along these lines so there is now a bug > filed for tracking > purposes:http://code.google.com/p/gdata-issues/issues/detail?id=997 > > Leni. > > Zindus Development wrote: > > Hi Trevor, I should have provided a one-sentence summary :-) Here it is: > > I think the API didn't provide an <entry><gd:deleted/></entry> > > element when it should have. > > > I'll send you some details off-list. > > > Leni. > > > Trevor Johns wrote: > >> On Wed, Oct 15, 2008 at 2:24 PM, Zindus Development > >> <[email protected]> wrote: > >>> Hi - > > >>> I'm seeing a sequence of interactions with the API that I'm finding > >>> confusing. It looks to me like it's a bug at Google but perhaps there's > >>> another explanation. > > >>> Here's what happened: > >>> - client created a contact - http status: 201. <id> is 1234 > >>> - GET http://www.google.com/m8/feeds/contacts/[email protected]/thin? > >>> showdeleted=true > >>> <entry> for <id> 1234 is present as expected. > >>> - time passes > >>> - POST to the edit url (X-HTTP-Method-Override: DELETE) > >>> http status: 404 > > >>> This 404 was unexpected! The client hadn't seen a tombstone for the > >>> <id> 1234! > > >>> One possible explanation is that the API didn't supply a tombstone when > >>> it should have. > > >>> To test that hypothesis: > >>> GET http://www.google.com/m8/feeds/contacts/[email protected]/thin? > >>> showdeleted=true > >>> now shows a tombstone for <id> 1234. The <updated> element on the > >>> tombstone is 2008-10-13T21:41:35.000Z which I assume indicates when it > >>> was deleted. > > >>> When I go back and look at the GET in which this tombstone should have > >>> appeared, it's not there. The GET I would have expected to see it is: > >>> GET https://www.google.com/m8/feeds/contacts/[email protected]/thin? > >>> showdeleted=true&updated-min=2008-10-13T21:40:58.000Z > > >>> The response <feed> contains: > >>> <updated>2008-10-13T21:41:41.806Z</updated> which indicates that it > >>> should contain the tombstone. But it doesn't. Instead it contains an > >>> <entry> for <id> 1234. So something is wrong. > > >>> I hope this isn't too long-winded and difficult to understand. If it'd > >>> be useful I'd be happy to share some details of the account off list. > > >>> Thanks. > > >>> Leni. > >> Hi Leni, > >> I'm not sure I'm following what's going on here. Are you saying that > >> the entry doesn't have a <gd:deleted> element if you set the > >> updated-min parameter? Or is something else the problem? > > >> Feel free to send me logs off-list, if you think that will help. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
