QUOTE(Deirdre @ Apr 29 2008, 01:52 PM) [snapback]595186[/snapback]
RSS actually usually increases (rather than decreases) server loads.
I think you're assuming a poor implementation and excessive polling on the part of clients with no offloading to secondary services to cache requests.
I don't think this is necessarily the case if it is done properly. If the RSS feed is generated as a flat XML file periodically from new messages (say once every 15 or 30 minutes) then the operation of polling the RSS feed is nothing more than a simple HTTP GET of a static file; there are no per-GET database queries involved whereas there are always many DB queries involved when someone actually visits the site since these can't really be cached or delayed.
Furthermore, even the HTTP GET of the RSS XML can be offloaded onto other sites that cache the feed. Web based RSS readers will generally do this internally anyway; even if 1,000 people are using google reader to read the site's RSS feed, google reader will poll once periodically for all 1,000 people.
No fancy logic is really needed to create multiple feeds for different forums or anything either. Something like Yahoo Pipes could be used to implement this logic off server, though I'm not sure how intelligent Yahoo Pipes is about its caching.