since leech is currently being revamped, i have a propsition.. Dunno if it's feasble but i think it would simplify things alot.

Why don't we use the functions of the official aggregator module to parse feeds? i know in the past the official aggregator couldn't parse atom feeds. But now it does. This would simplify the module, reduce maintenance task, remove code redundancy...

Anyone knows if it's doable?

Comments

alex_b’s picture

alex_b commented

Hi zis,

leech does read atom feeds (e. g. : http://news.google.com/news?hl=en&ned=us&q=washington+dc&ie=UTF-8&output... )

although i would really like to get rid of maintaining leech's own parser, i would like to be sure that what we are switching to is fundamentally better and can be integrated in a manageable timeframe.

a comparison in performance and accuracy of our options would be the next step. in addition to the aggregator's parser simple pie http://simplepie.org/ would be a candidate.

then - of course - we would have to figure out how to build it in neatly...

improving leech's parsing capabilities would be very good, i just don't find the time and the energy to do it right now.

alex

alex_b’s picture

alex_b commented

it would also be cool to somehow plug in to the feedparser that budda is creating as a replacement for aggregator: http://drupal.org/project/feedparser .

zis’s picture

zis commented

Actually i was talking about the aggregator module not parsing atom feeds.. (before 4.6 i think)..

if feedparser gets into core or at least becomes the default parser in drupal it would be great and should be used.. acutally that was my idea; to use one parser for all feeds in drupal instead of each module having its own parser.

alex_b’s picture

alex_b commented
Priority: Minor » Normal

i am with you, zis - we should get that one done. I bump the priority up to normal - the feed parsing performance of leech is vital.

alex