[twitter-dev] Destroy Tweet Problem

2010-07-08 Thread quenotacom
Hi,

I am having the following problem when trying to delete a tweet from
my app:

After selecting the tweet to delete or (destroy), I send the xmlhttp
with the destroy sentence specifying the ID to
delete, the ajax return a 200 code with the info of the tweet being
deleted (i thought the commit was done) ... and ... sometimes it works
and sometimes it reappears !, I checked the twitter site when i try to
delete the tweet from my app and sometimes after deleting ...  it is
still available in the twitter site, after two or three times it is
deleted ... but it looks like you have more than one copy of the tweet
and depending the syncronization there is a process that recreate the
tweet ... I reviewed my code to check no cached data was in my app but
i access using a random number in the URL to avoid cache

Any help appreciated.
Thnks
quenotacom


Re: [twitter-dev] Destroy Tweet Problem

2010-07-08 Thread Matt Harris
Thanks for letting us know about this. Can you file this as a defect on our
issue tracker: http://code.google.com/p/twitter-api/issues/list
I know there have been other reports of this but I haven't seen a ticket
issue for it yet.

Thanks,
Matt

On Thu, Jul 8, 2010 at 4:20 PM, quenotacom webmas...@quenota.com wrote:

 Hi,

 I am having the following problem when trying to delete a tweet from
 my app:

 After selecting the tweet to delete or (destroy), I send the xmlhttp
 with the destroy sentence specifying the ID to
 delete, the ajax return a 200 code with the info of the tweet being
 deleted (i thought the commit was done) ... and ... sometimes it works
 and sometimes it reappears !, I checked the twitter site when i try to
 delete the tweet from my app and sometimes after deleting ...  it is
 still available in the twitter site, after two or three times it is
 deleted ... but it looks like you have more than one copy of the tweet
 and depending the syncronization there is a process that recreate the
 tweet ... I reviewed my code to check no cached data was in my app but
 i access using a random number in the URL to avoid cache

 Any help appreciated.
 Thnks
 quenotacom




-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris