Comment Simple solutions (Score 1) 443
People, if you are going to serve up a popular RSS feed, use a seperate server (or servers). You can't control the clients so you have to be prepared to handle the worst case. Other than bandwidth, an RSS feed should never cause your site to stop handling requests for your site. Be prepared to put a caching appliance in front of your RSS feed if it's *really* popular (/.?)
That said, the client software should poll at intervals related to the start of the application and they should not retrieve the RSS unless it has changed since the last retrieve (hint: use HTTP HEAD). Developers should be shot if they are too lazy to implement these simple 'net friendly features.
That said, the client software should poll at intervals related to the start of the application and they should not retrieve the RSS unless it has changed since the last retrieve (hint: use HTTP HEAD). Developers should be shot if they are too lazy to implement these simple 'net friendly features.
