9 ms·
Interesting practical problem. I've tried mentioning a few solutions you might try here: http://dhruvbird.blogspot.com/2012/11/twitter-api-y-u-no-respond-fast-w
by dhruvbird 14y ago
Interesting practical problem. I've tried mentioning a few solutions you might try here: http://dhruvbird.blogspot.com/2012/11/twitter-api-y-u-no-respond-fast-why.html http://dhruvbird.blogspot.com/2012/11/twitter-api-y-u-no-res...
- mittermayr 14y agoi responded on your blog. i am using solution 3 already, it helps a bit but doesn't help with the core problem.
- dhruvbird 14y ago@mittermayr I responded to your comment too :) There isn't much you can do about the latency at their end except try and get the most out of your API quota by making sure you don't issue a call when you know you will time out (discussed in the reply). I would be interested in knowing other solutions that work for you.