Awasu » How to kill RSS
Monday 14th July 2003 10:29 AM [General]

I've been having an interesting (to say the least) discussion with one of our users about why Awasu imposes limits on how often a channel can be updated.

The reason is bandwidth. RSS is becoming very popular now and if thousands of people start requesting a feed from a web server every two minutes, that server is going to be struggling to keep up. The publisher may also be hit with an unwanted bill for excess bandwidth which would be particularly annoying since most of that bandwidth would have been a total waste i.e. updates on a channel that were un-necessary because nothing had changed.

I wouldn't be surprised if Awasu has the highest default time between updates of any aggregator - once per day - although you can easily change this down to anything as low as once per hour in the free Personal Edition. The Advanced Edition reduces this limit futher to once every half-hour and the Professional Edition to once every five minutes but these are paid versions and will have far fewer people using them.

So please be considerate when configuring how often your channels will update. Some publishers only write once a week and it would be pointless and counter-productive to update their channels every five minutes. A good way to kill RSS would be for people to make a nuisance of themselves, piss website administrators off and generaly make a bad name for RSS.

Blogging is about social interaction and community, so people, please be nice to each other!

One Response to this post

Taka wrote:

"A good way to kill RSS would be for people to make a nuisance of themselves, piss website administrators off and generaly make a bad name for RSS."

Like you said, RSS is really becoming popular. Once it takes off, it will feed (no pun intended) on itself just like P2P. Savvy people will be considerate, but not others. Restraints or controls will have to be instituted eventually. Check out this article.

http://computerworld.co.nz/webhome.nsf/UNID/7305E761CF352CE2CC256D5B007B1C2A!opendocument

Have your say