Re:Twitter’s poor API documentation practices
by polemic on Monday January 09, 2012 @06:16PM
(#3444794)
Really? An expected response from a foreign (uncontrolled) source brought you servers down?
Are you validating responses now, or just assuming they'll never change / always be correct?
Re:Twitter’s poor API documentation practices
by mattdeboard on Tuesday January 10, 2012 @04:09AM
(#3446274)
"Well, we got a string instead of an integer and yada yada yada, our network almost collapsed."
That's a pretty big "yada yada yada" you left out. I am going to assume there's a legit reason why getting a string back instead of another type of reason crippled your servers, but I'd like to know what it was.
Re:Twitter’s poor API documentation practices
by sutterbomb on Tuesday January 10, 2012 @12:18AM
(#3445810)
Yup same issue bit me once too - sorting tweets by their RT count doesn't work well when the count is no longer an integer. (Fortunately I was only building a little app for myself to try to learn Ruby and Sinatra.)
Thanks, Twitter!