Yes, I am dealing with the 502s by following up with a retry until it
succeeds. I have not come across any that did not succeed after a
second attempt. Just wanted to give the team a heads up. Not mission
critical at this point for me.
On Apr 2, 8:21 pm, jmathai jmat...@gmail.com wrote:
In my
and thanks for the heads up - we're investigating this to see if it
can e made more responsive when we're under load.
On Apr 5, 2010, at 6:05 AM, iematthew matthew.dai...@ientryinc.com
wrote:
Yes, I am dealing with the 502s by following up with a retry until it
succeeds. I have not come
Sorry, I hit the reply to author accidentally on my last reply. Sounds
like what's happening is a caching latency. I've set my script to do
an exponential backoff on the errors starting at 4 seconds, but none
of the attempts ever requires more than the 4 second delay. Until the
Twitter team can
In my experience you have to deal with 502s. I had a retry mechanism
in place which would retry a request up to 3 times if a 5xx response
was received. This was ≈ 6 months ago so I'm not sure the current
state of affairs.
On Apr 2, 11:47 am, iematthew matthew.dai...@ientryinc.com wrote:
Sorry,
