One of the key restrictions with the Twitter API is that any client IP address can only make x number of API calls per hour. If you’re making these API calls from your web server (which obviously only a static IP address), you could quickly use up your hourly allocation on a busy site. Twitter does allow you to “whitelist” your web application to give you a better hourly rate, but here’s a better way: Use the clients, ie your users, to make the API calls from their browsers.
Submitted by: JohnGalt Submitted on: Dec 16, 2009
This Tut has no comments. Be the first to add your two cents!
Login to post comments.
ie css regex codeigniter javascript php mysql mootools framework library ci mvc forms ajax blog regularexpressions world flash jquery dom rating svn dojo xml rss facebook xhtml nav navigation menu effect plugins jqueryui widgets twitter curl ui plugin wordpress event tinyurl photoshop apache google safari python mac apple search zend

For all the newest TUTs, follow @tutlist
NeilWilston (356 Tuts)
girish (232 Tuts)
kumaraman (203 Tuts)
showkatahmad (160 Tuts)
deepti89 (147 Tuts)
Drag TUTmark to your bookmarks
to begin using our bookmarklet.
Don't know how to use a bookmarklet?
Check out this tutorial.
Home Page (RSS and ATOM)
New TUTS (RSS and ATOM)
Subscribe by Email
To learn how to get your ad here.
CONTACT US TODAY!