You can call this command and check your rate limit: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0rate_limit_status
But mainly it's a common problem. It'll clear up in a few hours. I recommend caching if you want it to work 100% of the time. Rob On Sun, Aug 16, 2009 at 9:35 PM, mapes911<[email protected]> wrote: > > Hi all, > > We are developing a social network and part of the functionality is to > allow the user to enter their twitter user name and display their > public twitter feed on their profile. > > I am using Zend Framework and until recently, our testing was working > just fine. A user could simply enter their user name and we would > retrieve and display their timeline. > > Now, we are getting a connection timeout Error #110: Connection timed > out > Is this possibly because we are being rate limited? I doubt it because > we have no users yet.. just our own internal testing.. but I can't see > why this would just stop working. > > This is the line of code we are using > > $client = new Zend_Http_Client('http://twitter.com/statuses/ > user_timeline.json?screen_name=' . $user- >>twitter_id .'&count=50&page=1'); > $response = $client->request(); > > So we're basically just retrieving a json feed. > > Any ideas? > Thanks in advance >
