If you're basing your business on the Search API it definitely sounds as if you're not aware yet of the [mostly unofficially documented] limits and constraints [mostly just alluded to by John Kalucki and others through their exhortations on this list for people to rather use the Streaming API] on using the Search API.
If your application is based on the assumption that you can throw an unlimited [or even just a reasonably elevated] number of queries at the Search API as and when your app needs scaling or hits a volume spike, you will be wise to rethink your approach. On Feb 13, 4:03 pm, Umashankar Das <umashankar...@gmail.com> wrote: > We ,as a team , have planned on working with a worst case scenario. > twitter's search API is very important to us. We never planned for > whitelisting, we dont need it. The only worry is if tomorrow, (hopefully), > if we generate traffic from our product, will twitter just stop the 'SEARCH > API' . We need to know that. -- 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
