If you are sending calls at the same instant, make sure to use a
different nonce value for the calls or things will certainly go goofy.
-Chad

2009/8/26 Cristovão Morgado <cristovao.morg...@gmail.com>:
> All my retry s are done some 100ms after the receiving the 401's.
> Another thing I've noticed is if I try to call the API for 2 users in the
> same instant I get a 401.. I avoid that separating call by some
> milliseconds...
> Otherwise all is fine (in 3 months I've posted 100.000 tweets) :)
>
> On Wed, Aug 26, 2009 at 4:16 PM, Andrew Badera <and...@badera.us> wrote:
>>
>> Sometime later, or moments later? 401s, outside of rate limiting, seem
>> to happen when the system's stressed or otherwise flaking out. Try
>> recalling the operation 2-3 times, gently so as not to slam the
>> servers, if you receive a 401 initially.
>>
>> ∞ Andy Badera
>> ∞ This email is: [ ] bloggable [x] ask first [ ] private
>> ∞ Google me:
>> http://www.google.com/search?q=(andrew+badera)+OR+(andy+badera)
>>
>>
>>
>> 2009/8/26 Cristovão Morgado <cristovao.morg...@gmail.com>:
>> > I have an application using oAuth to get users timeline, mentions etc.
>> > The strangest thing is without any change some users start to get 401,
>> > and
>> > them sometime later it starts to work again.
>> > Any ideias why?
>> > CM
>
>
>
> --
> Cristovao Morgado
> aka Saintr
> http://www.oMeuJogoUsado.com
> http://www.TweetaPorSMS.com
> http://twitter.com/TheSaintr
>
>
>

Reply via email to