When you have a web service like Twitterlive that uses several third party APIs in order to work properly is always difficult to make sure you handle all the potential errors correctly because there are instances when the third party remote service is down and that causes you own service to fail.
That’s why in order to handle this potential errors I took several months of planning and testing twitterlive to make sure the service was reliable and able to handle a large volume of feeds.
One important part was to make sure the service would be scalable and strong from the ground up; so I decided to manage all the heavy duty tasks such as importing and publishing of feed items from a separate server and running as a desktop service that would not affect the performance of the twitterlive.net site in any way; the advantage of doing this is that even if the web site twitterlive.net is down your updates keep publishing to twitter.
The url shortener part of the service is also run from a different domain name so the traffic from each site would not affect each other. Twlv.net is just a simple page that does nothing else than to redirect the short urls.
As we have seen from other twitter feed services that have had a fair share or reliability issues is important you you plan accordingly and provide a top of the line service to your users.
Look no further; twitterlive is the best service to feed your blog to the social media sites.

In order to get the latest news and updates about the service
www.twitterlive.net A better way to feed your blog to twitter.













































.gif)


