WordPress.org

Why Static Feeds?

It's all about web server performance. It is much more efficient for a web server to serve a static XML file than to dynamically re-create the feed in PHP/MySQL upon each request. Since a blog feed doesn't change as often as it is downloaded, it makes sense to serve this information as a static file.

What else do you recommend?

Combine this plugin with a web server configured with compression (mod_deflate in Apache) and a PHP Accelerator (such as APC), and you have yourself a real WordPress serving powerhouse!

Will this plugin work with other caching plugins?

It may work, but I wouldn't guarantee it. If you're using this plugin with another caching plugin without problems, let me know and I'll start a list of Static Feed compatible Caching plugins.

Do I need this plugin if I am already using a caching plugin?

Most likely no since the caching plugin may be doing something similar.

Does Static Feed handle category, tag or comment feeds?

Not yet, sorry.

I previously switched from Movable Type to WordPress, can this plugin continue to maintain my original Movable Type feed?

Yes! This is what version 1.0 of this plugin was originally written for. Simply configure this plugin to write to the appropriate xml file on your server and you're all set.

What is Web Server Compression?

Web server Compression is when the web server compresses the data before returning it to the client (web browser). Compression will shrink XML to more than half its normal size, resulting in less bandwidth and a faster downloading experience for the end user.

You can test your site and feeds for compression by using the What's My IP HTTP Compression test.

Note: This plugin does not add HTTP Compression to your web server. HTTP Compression is a feature your web hosting providor or administrator would configure.