Server or client side for receiving tweets?

I launched this website for my father, who extracts tweets from his twitter and displays them in an alternative format. Currently, tweets are pulled using javascript so completely on the client side. The most effective way to do something? There is an unrated place on the website, but I'm just wondering what the best way to scale it would be. Any advice would be appreciated. I am also thinking of including articles in the stream at some point. What would be the best way to implement this?

+5
source share
6 answers

Twitter API requests are limited to 150 hours . If your page is being requested more, you will receive an error message from the Twitter API (HTTP error 400). Therefore, it is probably best to request tweets on the server and cache the response for a certain period of time. You can request the latest tweets up to 150 times per hour, and whenever your page is requested, it receives cached tweets from the server side of the script, and does not directly call the API.

From Twitter docs:

Unauthorized calls allowed 150 requests per hour. Unauthenticated calls are measured against the public IP address of the server or device making the request.

API Twitter , . , , . .

+7

API Twitter. . js- , , js .

? ?

+1

, . , , -.

, , . , ( , , , Twitter;))

0

. ,

0

, , ! . . , . -, ! ! !

api, , .

0

, . , . (, - ) , AJAX, , . , , , - , .

0

All Articles