I have been subscribing to RSS feeds for some time now, but it was not until I had to implement one that I realised that there was more to it than just a structured XML response.
Below is a quick dissection of what I would consider the absolute minimum implementation for an RSS feed. I’m calling it “wallet friendly” not because it makes you money, but because it will save your users in bandwidth costs by not spitting out a full feed for every request. Whilst the example is in Java, using Rome and Webwork, the details apply equally well to other frameworks and languages.
This example is an extension of the WebWorkResultSupport class.
protected void doExecute(String format, ActionInvocation action....
{
HttpServletResponse resp = ServletActionContext.getResponse();
HttpServletRequest req = ServletActionContext.getRequest();
OgnlValueStack stack = actionInvocation.getStack();
Firstly, what do we do if there is no feed to display? The answer will depend on what that means in your system. If it’s an error, then it’s time for a 500 (Internal Server Error) response. If, on the other hand, it means that the feed request is invalid, it’s best to return a 410 (GONE) so that whoever is making the request knows that they should stop.
SyndFeed feed = (SyndFeed) stack.findValue("feed");
if (feed == null)
{
resp.sendError(HttpServletResponse.SC_GONE);
return;
}
Now set the content type and disposition. This will help the browser to deal with the response appropriately, and give it a friendly name if the user decides to ’save as’.
resp.setContentType("application/rss+xml; charset=UTF-8");
resp.setHeader("Content-Disposition", "filename=rss.xml");
When handling an RSS request, you should not return the feed unless it has changed since it was last requested. You can find a very good discussion on this by Charles in his fishbowl, and by Randy at the kbcafe. (For those in a hurry, the relevant details are that the “Last-Modified” and “ETag” headers are returned in the following request as “If-Modified-Since” and “If-None-Match” respectively)
There are two steps to this. The first is to always set the “Etag” and “Last-Modified” response headers. The “Last-Modified” details can be taken from the feed as so:
// A happy default here is the If-Modified-Since header.
// If we don't have any feed entries, then this will result
// in a 304 Not modified
Date lastModified =
new Date(request.getDateHeader("If-Modified-Since"));
List entries = feed.getEntries();
if (entries.size() > 0)
{
// Get the latest feed entry - assuming the latest is
// at the top and that you set a published/updated
// date on the feed entries.
SyndEntry entry = (SyndEntry) entries.get(0);
lastModified = entry.getPublishedDate();
Date updated = entry.getUpdatedDate();
if (updated != null && lastModified.compareTo(updated) < 0)
{
lastModified = updated;
}
}
The Etag should uniquely identify this feed (read – the latest item in this feed). Unless you expect feed entries to be created at exactly the same time (or your database does not provide a high degree of accuracy in the time field) it’s sufficient to use the last modified timestamp for the Etag. If this is not unique enough in your case, you will need to create a unique hash from the content.
String etag = Long.toString(lastModified.getTime());
resp.setHeader("ETag", etag);
Before you can use the last modified date for the header, you may need to drop the milliseconds since they are not part of the date format used by HTTP.
Calendar cal = Calendar.getInstance();
cal.setTime(lastModified);
cal.set(Calendar.MILLISECOND, 0);
lastModified = cal.getTime();
Now we can set the “Last-Modified” header.
// always set
resp.setDateHeader("Last-Modified", lastModified.getTime());
That completes the first step (setting the “Last-Modified” and “Etag” headers on every response). The second step is to check the “If-None-Match” and “If-Modified-Since” on the request (remembering that they ’should’ contain what you sent our in the previous response). If they match the “ETag” and “Last-Modified” values we just set on the response then we do not need to return the feed. A 304 Not Modified will suffice.
// Check the headers to determine whether or not a response
// is required.
if (TextUtils.stringSet(req.getHeader("If-None-Match")) ||
TextUtils.stringSet(req.getHeader("If-Modified-Since")))
{
if (etag.equals(req.getHeader("If-None-Match")) &&
lastModified.getTime() ==
req.getDateHeader("If-Modified-Since"))
{
// If response is not required, send 304 Not modified.
resp.sendError(HttpServletResponse.SC_NOT_MODIFIED);
return;
}
}
Now, let’s generate the feed data and send it on its way.
// Render the feed in the requested format.
WireFeed outFeed = feed.createWireFeed(format);
outFeed.setEncoding("UTF-8");
new WireFeedOutput().output(outFeed, response.getWriter());
resp.flushBuffer();
Oh, and one last thing. If you want to return error details when things go wrong, do the RSS reader a favour and format the error response in valid RSS format. But be sure to set appropriate Last Modified and Etag header. For example, set an error token in the ETag header that you can check next time round. If your current error token matches the ETag in the request, respond with the 304.
——-
Into continuous integration? Want to be? Try pulse.
.
), there is still a greater chance of a submit race. For large teams the continuous integration server can also be a great way to communicate recent project activity, as developers are notified of builds, and the web UI may allow you to see recent project changes.
