Thanks for the reply and the pointer !

2009/7/20 Doug Williams <d...@twitter.com>:
>
> Kevin,
> Please do not bump your thread here. It adds no value and contributes noise.
>
> That said, there is an open issue for this [1]. Be sure to add a star
> to receive updates to the defect. The defect is due to a replication
> delay and typically takes less than 90 minutes for the replication to
> reach the object serialized by the API. I'm still working on who
> actually owns this defect and will update the thread in the issue list
> when I learn more.
>
> 1. http://code.google.com/p/twitter-api/issues/detail?id=758
>
> Thanks,
> Doug
>
>
>
>
>
> On Mon, Jul 20, 2009 at 11:56 AM, Kevin  Dunglas<dung...@gmail.com> wrote:
>>
>> Nobody has the answer? It helps me a lot!
>>
>> On Jul 19, 6:42 pm, Kevin  Dunglas<dung...@gmail.com> wrote:
>>> Hello,
>>> I'm working on a program which update periodically some Twitter
>>> accounts avatars.
>>> Here is the process:
>>> --
>>> while True:
>>>   GEThttp://twitter.com/users/show/myuser.xml
>>>   GET avatar located at the url specified in the profile_image_url XML
>>> tag
>>>   Make some change to the avatar
>>>   POST the new avatar onhttp://twitter.com/account/update_profile_image.xml
>>>
>>>   sleep(some time)
>>> --
>>>
>>> While the program sleep (between two avatar processing) the user can
>>> upload manually a new avatar.
>>>
>>> My problem is that the value profile_image_url is often outdated an
>>> when I try to download the current user avatar using this value I get
>>> a 404 error.
>>>
>>> I guess the address of the avatar is cached, but after how long the
>>> users/show page contains the new value? Is there a way to always the
>>> get the current (displayed on the twitter.com user profile) avatar ?
>>>
>>> Thanks !
>>
>



-- 
Kévin Dunglas

http://lapin-blanc.net
http://codenroll.com
http://linkedin.com/in/dunglas

Reply via email to