Note that from GAE, your search rate will be throttled significantly, as you are sharing the Search API with every other GAE project on a single IP.
-John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Tue, May 4, 2010 at 12:34 AM, nischalshetty <nischalshett...@gmail.com> wrote: > Woops, my bad. I meant a meta search that would make use of all third > party APIs to display the results. > > But I got your explanation. So if I intend to process the tweets and > make sense of it, the Streaming API is what I would need to take a > look at. But if I intend to get the search results and just display > them on my site, then I guess the search API is what I should use! > > Pretty much clears everything, so cool! Thanks a lot! > > -Nischal > > On May 4, 3:27 am, John Kalucki <j...@twitter.com> wrote: >> If you are going to build a search engine, you'll need all of the >> Tweets to search over them. For this, you'll want to take the Firehose >> of all public statuses. >> >> http://apiwiki.twitter.com/Streaming-API-Documentation >> >> You'll need a commercial data license to do this. Email api to get started. >> >> GAE currently does not allow standing connections to the Streaming >> API. Also, you'll need considerably more resources than GAE to build a >> search engine. You'll need dozens of cores and hundreds of spindles >> just to get started. >> >> -John Kaluckihttp://twitter.com/jkalucki >> Infrastructure, Twitter Inc. >> >> >> >> On Sun, May 2, 2010 at 5:28 AM, nischalshetty <nischalshett...@gmail.com> >> wrote: >> > I plan to build a search engine which would utilize the search APIs. >> > Should I be using the Twitter Search API or the Streaming API to do >> > the same? >> >> > What is the difference between the two and would the Streaming API >> > work on the Google App Engine? >
