[
https://issues.apache.org/jira/browse/NUTCH-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500133
]
Chris A. Mattmann commented on NUTCH-444:
-----------------------------------------
Hi Guys,
Okay, here is the way that I currently see this issue, and what to do with
this. There are three options:
1. keep parse-rss and parse-feed (worst, but still doable)
2. gut parse-rss with new code from parse-feed (probably the best choice)
3. blow away parse-rss and create new plugin in sources called parse-feed (also
a good choice)
So, the plan I am going to do is:
if(parse-feed contains a superset of the functionality of parse-rss){
choose option 2
}
else{
choose option 3 if and only if parse-feed is equivalent to parse-rss
choose option 1 otherwise
}
I've been lagging on this. I'll make some progress on getting a patch ready
this week.
> Possibly use a different library to parse RSS feed for improved performance
> and compatibility
> ---------------------------------------------------------------------------------------------
>
> Key: NUTCH-444
> URL: https://issues.apache.org/jira/browse/NUTCH-444
> Project: Nutch
> Issue Type: Improvement
> Components: fetcher
> Affects Versions: 0.9.0
> Reporter: Renaud Richardet
> Assignee: Chris A. Mattmann
> Priority: Minor
> Fix For: 1.0.0
>
> Attachments: feed.tar.bz2, NUTCH-444.patch, parse-feed-v2.tar.bz2,
> parse-feed.tar.bz2
>
>
> As discussed by Nutch Newbie, Gal, and Chris on NUTCH-443, the current
> library (feedparser) has the following issues:
> - OutOfMemory when parsing > 100k feeds, since it has to convert the feed to
> jdom first
> - no support for Atom 1.0
> - there has been no development in the last year
> Alternatives are:
> - Rome
> - Informa
> - custom implementation based on Stax
> - ??
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
