TwitterBrite as a Service. WTF
Saturday, May 8th, 2010Today, after a fair amount of testing and racking my brains debugging with well revived help of martygoldberg [1] [2] I’ve managed to finish and add to TwitterBrite, what I’m calling “TwitterBrite as a service”. WHAT I hear you scream software as a service! Thats a cloud thing! You’ve ranted against cloud computing.
Well firstly, I’m not against cloud computing, I just don’t think it’s everything to everyone. Secondly “TwitterBrite as a service” has nothing to do with cloud computing.
What it does have a lot to do is removing one of the drawbacks of desktop RSS to twitter clients.
With cloud based twitter clients, such as co-tweet and Hootsuite, you can post your RSS feed to their site and walk away. The tweets will keep being processed if your their or not. However with TwitterBrite you have to fire it up, leave it eating up memory, while your not using it as a client your just posting RSS feeds…
But not any more! Windows allows you to have programs called services, which sit in the background, using only very limited resources and they can be started when you start windows up; as you may well have guessed, thats exactly what TwitterBrite as a service is, a very small windows servers that uses the same database as the main TwitterBrite application but runs in the background.





