Quoting Vijay :
OK Tom, will queue it and spread it, that should give me more room.
But that still doesn't answer the question - how do the big companies
manage?
Do they have multiple IPs?
The *really* big companies - like Google and Microsoft - just connect
to the Streaming API "Firehos
Right, that makes sense.
On Mon, Sep 20, 2010 at 11:52 AM, Tom van der Woerdt wrote:
> Of course they do :-) Each server gets an IP and gets 2 requests per
> hour. With 20 servers that means 40 requests per hour. Besides, I'd
> assume that these services spread their requests properly an
Large companies, and anyone who wants sustained access to high-volume
Twitter data, use the Streaming API. The REST API is primarily for client
applications and very-small-scale integrations. Note that REST whitelisting
is unlikely for use-cases that are covered by the Streaming API.
-John Kalucki
Of course they do :-) Each server gets an IP and gets 2 requests per
hour. With 20 servers that means 40 requests per hour. Besides, I'd
assume that these services spread their requests properly and don't
update every hour. Just because you have 2 requests per hour doesn't
mean you can
OK Tom, will queue it and spread it, that should give me more room.
But that still doesn't answer the question - how do the big companies
manage?
Do they have multiple IPs?
On Mon, Sep 20, 2010 at 11:41 AM, Tom van der Woerdt wrote:
> Just don't and you'll be fine :-) Just queue the requests an
Just don't and you'll be fine :-) Just queue the requests and spread
them over a few hours. It may also help to setup a Twitter account, as
it will allow you to make 350 requests per hour instead.
Tom
On 9/20/10 5:38 PM, Vijay wrote:
>
> "You really shouldn't be planning for the case where ever
"You really shouldn't be planning for the case where every single Twitter
user uses your application"
Haha, I agree. Its just that I took a few thousand users randomly, and was
playing
with their publicly available stats, tweets etc and quickly hit the rate
limit. Hence
this question.
On Mon, S
You really shouldn't be planning for the case where every single Twitter
user uses your application ;-) When you get to 100 users, you request
whitelisting. When you get to 2 users, your server will have a
problem handling all the information and you'll need to get a second
server anyway.
Tom
I am not sure about 20k, but 150 is miniscule.
If I am collecting stats on a bunch of users every hour for example, I can
only
collect on 150 users, which is tiny, compared to 140 million users Twitter
has.
How do the big companies manage? For example, twittercounter claims to
have stats on 10 mi
20k per IP is a lot. It means that a server should make more than 5
requests per second to hit the limit, which is a lot.
About your options: no idea. Just make sure to use the proper functions
and try not to hit the limits? :-) 150 is a lot as well, most Desktop
clients don't hit it (didn't, unti
Hi,
Newbie question, so please bear with me.
I am experimenting with twitter API, but quickly found myself hitting the
rate limit
(150 without authentication, correct?)
How do the big sites get over the rate limit (tweetstats, twittercounter
etc)?
Twitter's documentation says they can white list
11 matches
Mail list logo
