Thanks Josh - much appreciated.
Jason
Hi Jason,
As far as im aware the widget does not actually get rate limited, i'm
sure i read somewhere that this was not included in the normal rate
limit (but don't quote me on that).
The best way is to use an effecting caching technique. If you cache
the content every x minutes you should be
Hi Josh,
Thank you for getting back to me.
If I was to provide a widget myself and make API calls, I would
certainly be above the 2 calls per hour (5.5tps).
I would therefore have to implement a caching layer.
Added complexity comes from the fact that there are several instances
of the web
Hi Josh,
Thank you for getting back to me.
I am currently at the stage of evaluating the best approach to use.
My level of transactions per second (tps) and data staleness
requirements may well push me over the whitelisted call rate at times
(2 per hour / 5.5tps ) even with caching. Some
To me it sounds like a setup that you could do with a centralised data
source.
I would be tempted to build some sort of Twitter proxy service which
all your requests go through. You could mimic the Twitter API however
yours could including a caching mechanism which would support all of
your other
