I'm not paging, but rather using a combination of max_id and count=200.
Also - not getting nearly 200 every time, mostly below 100
Adriaan Pelzer
putting you in touch with your crowds
http://www.wewillraakyou.com
http://www.wewillraakyou.comtwitter: http://www.twitter.com/adriaan_pelzer
Check for whether you include retweets.
Tom
On 7/4/11 12:34 PM, Adriaan Pelzer wrote:
I'm not paging, but rather using a combination of max_id and count=200.
Also - not getting nearly 200 every time, mostly below 100
Adriaan Pelzer
putting you in touch with your crowds
Ah - thanks. That makes sense.
Still, having to retry on empty results doesn't make sense, or is this
normal behaviour when not using pagination?
Adriaan Pelzer
putting you in touch with your crowds
http://www.wewillraakyou.com
http://www.wewillraakyou.comtwitter:
Thanks all - I managed to get this fixed.
The main thing to remember is to build in some kind of delay between
successive API calls. In my case I made it 200ms with linear backoff on
retries. I know this is documented for the streaming api's - wasn't aware
that it also holds for the REST API.
