Monday September 27, 2004 |
Tucu's Weblog [Alejandro Abdelnur] I don't contradict myself, I just change my mind. |
[Blogs.Sun.com HOME] | |
|
We've just released version 0.4 of Rome and Rome Fetcher. They are still marked as Alpha but we consider they are already stable for some serious use, we just want to do some sanity check (mostly classes, interfaces, methods and packages names) before we go with a Beta release (which we hope it will be the next one). We've been busy with this one, just check Rome Changes Log and Rome Fetcher Changes Log, 35 entries. A few highlights:
Post a Comment: Comments are closed for this entry. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Posted by Mark Derricutt on October 24, 2004 at 03:45 AM PDT #
I'm wondering how Rome ought to react when it gets, well, slightly "off" input. I'll focus on the length of the description field for an entry, since that's where I ran into a problem with some RSS 1.0 feeds.
In com.sun.syndication.io.impl.RSS090Generator (or somewhere in that class' inheritance tree, at any rate), there are hardcoded length limits set on some fields; for the description field, it's 500. So if Rome encounters an entry description longer than that while working with a feed, it throws a FeedException.
I'm 100% down with being strict in what one emits, but here seems to be a case where throwing the exception will cut you off from accepting some feeds which aren't irreparably ill-formed (and according to (e.g.) the RSS 1.0 spec (http://web.resource.org/rss/1.0/spec), 500 is merely a _suggested_ limit).
Anyhow, I realize there are a few directions one could go with this issue. One approach that seems reasonably ecumenical is truncating fields that are too long (I suppose one might have to check that doing so leaves you with a well-formed structure).
Posted by Adam Constabaris on December 10, 2004 at 11:30 AM PST #