ScottAllender.com

So lately, I've been clowning around with DotNetNuke's scheduler engine. I'm in the process of creating a Twitter module for DNN for my day job. Apparently, the day job's website and intranet are pounding the "hell" out of the Twitter API, causing none of the updates to show after a specific amount of API requests are passed (probably between 65 - 100).

How do I resolve the issue? Well, I decided to cache the requests in a database that I control via the RSS feeds that twitter provides. Doing that, and creating the corresponding user interface, enables me to "pound" my database as opposed to the Twitter API, which then ensures that content is always being displayed.

That's all great, but it stinks if I have to manually update the cache myself, which is where the DNN Scheduler comes into play. I created a scheduled task (I will do my best to post a blog later about it), and my life should have been hunky dory. Unfortunately, if you don't set up the scheduled task using the exact class name and assembly...

Read More »

Comments (1)

Thoughts from Scott Development/Virtualization