[twitter-dev] Search API Rate Limit??
My interactive exhibition program send search query per 5 sec. (http://
search.twitter.com/search.atom?q=love OR hate&since_id) And parcing
only firstpage(wthin 15 search result).
I received "Timeoutexception" when 3~4 hours after running.
I want to know why ㅜㅜ
bool ofxXmlSettings::loadUrl(string url){
bool loadOkay = false;
//std::string xmlString;
string xmlString;
// Register Poco HTTPStreamFactory
if(!HTTPStreamFactoryLoaded) {
HTTPStreamFactory::registerFactory();
HTTPStreamFactoryLoaded = true;
}
// URIStreamOpener may throw an exception
try {
// Open URI Stream
std::istream* streamOpener;
//istream* streamOpener;
path = url;
try{
URIStreamOpener::defaultOpener();
try {
streamOpener =
URIStreamOpener::defaultOpener().open(path); --> make error line
}
catch (Poco::Exception& e){
std::string what = e.displayText();
//string what = e.displayText();
cout< pStr(streamOpener);
//auto_ptr pStr(streamOpener);
// Copy Stream to string
StreamCopier::copyToString(*pStr.get(), xmlString);
// Load string
loadOkay = loadString(xmlString);
}
catch (Poco::Exception& e){
std::string what = e.displayText();
//string what = e.displayText();
printf("%s\n", what.c_str());
throw;
}
return loadOkay;
}
--
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
[twitter-dev] Search API rate limit change?
Hello, After the latest performance issues with the search api i have been seeing a lot of 420 response codes.From yesterday until now i only get 420 responses on the every search i make. In particular, i search for about 100 keywords simultaneously every 6 mins. Why is this happening? Was there any change on the Search API limit? Any help is greatly appreciated. Thanks, Zaver -- 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
[twitter-dev] Search API rate limit on some keywords
Hello, I am experimenting with the Search API using php curl to get results on multiple keyword searches (about 130). It works fine, although i have observed that sometimes some of the keywords get a 420 code? Any ideas why is this happening? Let me know if you want any more details on my part. Thanks Zaver -- 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
Re: [twitter-dev] Search API rate limit
Hi Shan, The Search API is anonymous so authenticating makes no difference to the rate limit there. If you are requesting a lot of information from the search API you may want to look at the streaming API instead: http://dev.twitter.com/pages/streaming_api The majority of search cases can be handled by the default filter limits available through the streaming API. Best, Matt On Tue, Jul 6, 2010 at 7:31 AM, Ramanean wrote: > I am developing a normal twitter search application > > Inorder to beat the search rate limit if I ask a user to authenticate > whether that would be helpful? > > Whether the calls made by the user for search api will be counted in > the user's account ? or whether that would be > > still counted as a call from the IP address of the website? > > I am little bit confused here... > > Thanks > Shan > > > -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris
[twitter-dev] Search API rate limit
I am developing a normal twitter search application Inorder to beat the search rate limit if I ask a user to authenticate whether that would be helpful? Whether the calls made by the user for search api will be counted in the user's account ? or whether that would be still counted as a call from the IP address of the website? I am little bit confused here... Thanks Shan
Re: [twitter-dev] Search API rate limit & IP address question
On 2 March 2010 14:05, eys wrote: > Hello there! I have two questions: > > First, I received an approval for whitelisting for my server's IP > address (as in, the IP number that I see when I log onto my webhosting > account). I'm currently building my application in Flash using AS3 and > after I've tested my project a few times, I'll get this error: > > "Error #2032: Stream Error...[my search request]" > > I assume this is rate limiting in action? If this were true then sometimes your request works and other times it doesn't. Is that the case? > I read on this discussion > board that whitelisting doesn't affect Search API. Does this mean I > will always be limited to some arbitrary (unpublished) search limit? > > Then, I noticed the IP address used for the GET request is the IP > address of the computer I'm using, NOT the IP address of my web > server. How is this happening even though I'm using a proxy installed > on my web server? Shouldn't the call be made from the server, not the > computer? > > There are multiple requests happening here. I assume the following, which may or may not be correct: - From your browser you call your app - Your app runs some call through the twitter API - Twitter servers process the call and send it back to your app - Your app returns processed code back to your browser >From the above processes your IP address is passed through by the Twitter API to the twitter service. I'd suggest try running your request from a completely different network and see what happens. > Thank you. I'm pretty new at developing applications, so any help or > advice is greatly appreciated! > -- Charles A. Lopez charlesalo...@gmail.com What's your vision for your organization? What's your biggest challenge? Let's talk. (IBM Partner)
[twitter-dev] Search API rate limit & IP address question
Hello there! I have two questions: First, I received an approval for whitelisting for my server's IP address (as in, the IP number that I see when I log onto my webhosting account). I'm currently building my application in Flash using AS3 and after I've tested my project a few times, I'll get this error: "Error #2032: Stream Error...[my search request]" I assume this is rate limiting in action? I read on this discussion board that whitelisting doesn't affect Search API. Does this mean I will always be limited to some arbitrary (unpublished) search limit? Then, I noticed the IP address used for the GET request is the IP address of the computer I'm using, NOT the IP address of my web server. How is this happening even though I'm using a proxy installed on my web server? Shouldn't the call be made from the server, not the computer? Thank you. I'm pretty new at developing applications, so any help or advice is greatly appreciated!
Re: [twitter-dev] Search API: rate limit response code not changing 12/16
Don't forget to update the changelong :-P Abraham On Tue, Dec 15, 2009 at 18:43, Wilhelm Bierbaum wrote: > On December 3rd, I announced on twitter-api-announce that the Search API > rate limit response code would change to HTTP 400 as of December 16th, 2009. > (http://bit.ly/6yIjEn) > > Based on feedback we've been getting, we won't be changing the response > code for rate limiting to 400. For technical reasons, this code will have to > change soon. We're considering feedback we've received to figure what makes > the most sense. We will be announcing the change to another 400-series error > code when it is apparent what is best. > > Thanks, > Wilhelm Bierbaum > Twitter Platform Team > -- Abraham Williams | Awesome Lists | http://bit.ly/sprout608 Project | Intersect | http://intersect.labs.poseurtech.com Hacker | http://abrah.am | http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Madison, WI, United States
[twitter-dev] Search API: rate limit response code not changing 12/16
On December 3rd, I announced on twitter-api-announce that the Search API rate limit response code would change to HTTP 400 as of December 16th, 2009. (http://bit.ly/6yIjEn) Based on feedback we've been getting, we won't be changing the response code for rate limiting to 400. For technical reasons, this code will have to change soon. We're considering feedback we've received to figure what makes the most sense. We will be announcing the change to another 400-series error code when it is apparent what is best. Thanks, Wilhelm Bierbaum Twitter Platform Team
[twitter-dev] Search API rate limit
I've noticed that the Search API page has recently been changed to say: "The standard API rate limiting is liberal enough for most use cases. If you find yourself encountering these limits, please contact us and describe your app's requirements." Recently, this page stated that the rate for search is not limited. A week ago, Alex Payne stated here that there is not limit on the search API use; is this still the case, and the wording on the API Wiki is irrelevant? Or has the 100 req/hr limit been imposed on the search API as well? If the search API has been limited, is there a possibility of adding an authenticated search so that developers can apply for rate limit increases via their accounts, rather than a static IP that may not be feasible for their application? Thanks.
