My webhost says it is creating a lot of “sleeper” processes on the database server, and using up a lot of the processor resources. My account was even suspended until I fixed it.

SO – I am going to be rewriting the whole thing, pretty much from scratch now, and it will only be loosely based on Dan’s version…

Currently, the code will run through the database of posts, and find those that have shortened URLs stored for them, run a twitter search, and return/parse/store/display the resulting tweetbacks. And it does this every 5 minutes.

However, that sucks up a lot of processing power to do that, especially if you have a big blog, popular blog, or both. The Answer: A Rewrite. This one is going to run a single Twitter search for every shortened url in the database, return ALL the results once, and parse them out, store them in the database, and associate them to their respective parent posts.

So, there’s the update for why this hasn’t been released yet.

I’m also working on trying to get the retro-active TweetThis buttons working on old posts – but something isn’t working right – either it’s the original code that isn’t comparing what’s in the database to the conditional statement correctly (if this.url = “”, then make new ones), or something. It’s going to take some more testing on my own test database, since my webhost is getting antsy with all the processes I’m using.

I’ll keep everyone updated as it moves along. Thanks.

Technorati Tags: api, code, database, MySQL, Ping.fm, plugin, Programming, tweetback, tweetbacks, TweetSuite, webhost, WordPress