Save bandwidth by aggregating RSS feeds into an Exchange public folder

Learn how you can alleviate bandwidth and performance issues associated with heavy RSS feed usage by aggregating the content into an Exchange public folder.

Please let others know how useful this tip is via the rating scale at the end of it. Do you have a useful Exchange or Outlook tip, timesaver or workaround to share? Submit it to SearchExchange.com. If we publish it, we'll send you a nifty thank you gift.


RSS feeds are an increasingly popular and powerful way to wade through many Web sites' worth of information at once. In big organizations, though, that can mean thousands of people hitting the same feeds over and over again all day long, sometimes as often as every 10 minutes.

This means a lot of bandwidth usage, not to mention a strain on the servers providing the feeds. But banning the use of RSS isn't realistic, since it's sent over conventional HTTP connections -- and it's ultimately far too useful to users to dispense with entirely.

Exchange Server developer Glen Scales has come up with an interesting solution to the performance issues associated with heavy RSS feed usage. He's written a script that aggregates RSS feeds and places them into an Exchange public folder as a series of posts.

Instead of accessing RSS feeds on their own and running up lots of redundant connections, users can simply go to an Exchange Server public folder (a local connection) to read what's posted there.

Obviously an administrator needs to set up the script to aggregate the desired RSS feeds, but if many people are reading the same feeds anyway, it's clearly more efficient and worth that minimal effort.

The script is a .VBS script that needs to be run from the command line on the Exchange server where the public folders are hosted. Multiple feeds can be aggregated into one folder, or each feed can have its own folder if you so choose. Atom, RSS 2.0 and RSS 1.0 RDF are all supported feed formats.

One of the challenges Scales faced was to read the RSS feeds in such a way that they would only be reread when something changed. He was able to do this by adding two content headers into the GET command that obtains the feeds.

If-Modified-Since and If-None-Match tells the server to only provide a new feed if there's new material. He also used the Accept-Encoding header to use compression on the returned data, but there are some Web servers that don't correctly honor all of these headers. Scales estimates that only some 40% of the blogs or feed providers he's tried this script with supported compression.

About the author: Serdar Yegulalp is editor of the Windows Power Users Newsletter.

Do you have comments on this tip? Let us know.

Related information from SearchExchange.com:

  • Learning Guide: An administrator's guide to Exchange public folders
  • Learning Center: A primer on Exchange public folders
  • FAQ: Exchange public folder management
  • Tutorial: Exchange public folder permissions
  • Tutorial: Indexing Exchange Server public folder content
  • Reference Center: Exchange public folder tips and resources
  • This was first published in April 2006
    This Content Component encountered an error

    Pro+

    Features

    Enjoy the benefits of Pro+ membership, learn more and join.

    0 comments

    Oldest 

    Forgot Password?

    No problem! Submit your e-mail address below. We'll send you an email containing your password.

    Your password has been sent to:

    -ADS BY GOOGLE

    SearchWindowsServer

    SearchEnterpriseDesktop

    SearchCloudComputing

    SearchSQLServer

    Close