Hi, Max,
First of all, this is just from personal experience with my own application,
so, take it with all the necessary grains of salt about rate limits changing
based on traffic and time of day, your searches being different from mine,
etc, etc.
My experience has been that I tend not to run into trouble if I can stay
under 20 search API requests per minute, and that if I do go over, I'm
typically only rate-limited for a few minutes. So, if you can either reduce
the frequency of your search calls to every 15 seconds instead of every 10,
or can tolerate a few of them failing once in a while, you should be fine.
You mention four different CPU's -- are they searching for different things?
If so, you might consider just having one CPU do a single search request
every 10 seconds, stringing the four original searches together with OR's --
I've had great success using this method to batch what would've been up to
50 different searches into a single API call.
You mention an art installation -- if your problem is that you've got the
software to put interesting twitter-driven graphics on one monitor with one
CPU, but your installation needs four monitors, so, it's easiest to just run
the same software on four different CPU's, I'd say this is exactly the kind
of scenario where Twitter would encourage you to make more efficient use of
the API calls. Were I in your shoes, I'd think about setting up one master
server, which would run a script to search Twitter every 10 seconds and dump
the resulting JSON into a flat file. The master would also be running Apache
to serve that flat file up over HTTP, and any number of slave machines
showing interesting graphics could hit your master server instead of
Twitter. Other than changing what URL they hit for data, you wouldn't have
to change the show-interesting-graphics code at all, since the master would
be serving up the exact same data the slaves would've gotten from Twitter
directly.
Best of luck,
-Alex
On Thu, May 19, 2011 at 6:26 AM, Max maxdo...@googlemail.com wrote:
Hello, for an art installation i will be having 4 cpus running the
search twitter query (search.twitter.com) . because the rate limit is
not made public, if you could authorize my proposed request frequency.
if i have each computer (on the same IP adress) calling the search api
every 10 seconds, that comes to 1440 calls per hour (from the same Ip
adress) whilst also simultaneously running the sample stream (on each
cpu) . would this be allowed?
it would be between June 16th and June 24th, continuously during day
time hours.
thanks alot.
max
maxdo...@gmail.com
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker:
https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
--
Alex Feinberg
CTO, Trak.ly
http://trak.ly/
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
