Hello,

I am going to develop an application that is doing large-scale
analysis of twitter data for scientific purposes at my university. The
idea is to get the data needed with as less load for twitter as
possible and do the complete analysis client-side. Every piece of data
is supposed to get fetched exactly one time, and not more often.
I am going to have a set of public twitter users of which I want to
get as much of past public twitter statuses as possible, and
continuously fetch all new public statuses.

During my search through the documentation of the Twitter API and this
group, some questions arose.

1) It seems that the Site Streaming API is the correct one for my use
case. Is that correct?
2) It seems that I have to create a twitter account if I want to use
the API. Is that correct?
3) On http://dev.twitter.com/pages/rate-limiting#streaming, I get
pointed to the documentation of the Streaming API, but I can not find
any limits similar to the ones of the other APIs. The only thing that
seems to be restricted is the amount of connections at one point in
time (and the number of times I try to reconnect of course). Am I
missing something or is it indeed that open?
4) I have found several Java libraries simplifying the usage of the
twitter API. None of them, though, seemed to be aiming at large-scale
usage, but rather user-oriented client interfaces for twitter. Maybe I
missed something; in that case, please give me a hint on which library
might be able to do the job.

Thank you very much in advance.

With kind regards,
  Florian

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Reply via email to