Yes.. I was expecting 350 oauthenticated calls per hour but was not
able to find it after OAuth. It is still giving me the 150 rate limit.

Thanks.


On Nov 27, 5:06 am, Edward Hotchkiss <edw...@edwardhotchkiss.com>
wrote:
> it's 150 requests for flat file data per hour and 350 oauthenticated calls 
> per hour ... unless you use a proxy. :P
>
> On Nov 26, 2010, at 2:55 AM, m36tb6ll wrote:
>
>
>
>
>
> > Hi! I am a newbie in the field and am working on my first twitter web
> > app. I have created a variable loop timer using rate_limit_status
> > which works well in maximizing the usage of the twitter API without
> > going over the hourly limits.
>
> > Now that I have incorporated OAuth, I was expecting to see the limit
> > increase from 150 (unauthenticated requests) to 350 (authenticated
> > requests). But, I am still seeing the 150 limit both in the response
> > headers and Firebug when calling rate_limit_status API after OAuth.
>
> > Is there something I'm missing here?
>
> > Your help would be greatly appreciated. Thanks in advance...
>
> > --
> > 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
>
> Regards,
>
> --------------------
> Edward Hotchkiss
> edw...@edwardhotchkiss.comhttp://www.edwardhotchkiss.com/
> --------------------

-- 
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