Blogging Roller

I've been watching RSSLibJ for a while and wondering whether we should use it here in Roller. RSSLibJ is a Java class library that allows one to create RSS output in a variety of formats including RSS 0.9X, 2.0, and RDF from a single object model (RSSLibJ is not suitable for RSS parsing because it does not handle badly formed feeds). So, does it make sense to use RSSLibJ for RSS output in Roller? I'm pretty sure the answer is no because:

• Why bother? All RSS aggregators worth consideration already support RSS 2.0, adding support for RSS 0.91, RSS 0.92, RSS 1.0, and RDF does not really add any value to Roller.


• If it ain't broke, don't fix it. Roller already supports RSS 2.0 output using a simple Velocity template that duplicates Mark Pilgrim's RSS 2.0 MT template (you can't get more perfect than the Pilgrim ;-).


• Templates are easier to maintain. If we have a output format problem with RSSLibJ, we'll need to grok the RSSLibJ Java code, tweak RSSLibJ, recompile the jar, and if we want to do things "right" we'll need to submit a patch to the RSSLibJ folks. If we have a format problem with our current solution, we just tweak a simple Velocity template and fix it (worst case: we also have to modify our object model).


• What about performance? More than half the traffic on a big Roller site (e.g. FreeRoller) is RSS traffic, so RSS production needs to be pretty efficient. With support for If-Modified-Since and RSS output caching, this is less of an issue, but it is still an issue. Converting our existing object model of WeblogEntries, WeblogCategories, Comments, etc. into a separate RSSLibJ object model before output can commence seems like a pretty inefficient exercize in terms of memory usage and speed.

If you want to tell me how wrong-headed I am on any of these points, I welcome your comments and trackbacks.

Tim Bray: Standards have nothing to do with innovation; a good standard is what happens when an industry has basically shaken the bugs out of a technology and then, after the fact, writes it down. This is true of all the really successful standards: grams and meters, voltage, the calendar, octane ratings, TCP/IP, XML.

Tim says its time for standardization of RSS, explains why and asks who will do it. Sounds like he favors IETF. Don Box likes OASIS.

In case you missed it, as I did, there were very interesting discussions concerning RSS taking place all over the blogosphere yesterday. I believe they were all kicked off by this:

Dave Winer: Here's how Microsoft is going to fuck all of us. Their blogging tool will support RSS 2.0. Basic stuff like title, link, description, and maybe to be nice, a few extras like guid, category, and generator. Then they're going to define a namespace with poorly documented stuff the rest of us don't understand. [...] Now get this -- it doesn't have to be that way. We could establish a profile of RSS 2.0 and implement strict compliance with that profile in the major blogging tools.

Sam Ruby's site was the focal point of the discussions that followed because Sam has comments on his site and because, of course, Sam is the man. For a recap, look at Sam's Saturday and Sunday archives. Who joins in and posts the first cut of this profile? Don Box of Microsoft.