Didn't notice this thread in development. I'll read it in detail later today.

In the meantime, I was pointed to this link by a friend of mine which shows that simplePie is a complete no-no. This actually compares three of the contributed aggregation modules in terms of performance, my aggregation module is included in the comparison.

The aggregation module requires PHP 5 (since I use simpleXML), provides an API, and if you take a look at the issue queue you'll find that you don't need any external libraries to get very stable behavior. Aside from the initial wave of bug I got after completing it, I haven't received a bug issue in two months or so. SimplePie is forbiddingly performance terrible, or so I understood from Aron Novak's article which you can view below.

http://groups.drupal.org/node/4519

On 6/19/07, Boris Mann < boris@bryght.com> wrote:


On 6/19/07, Alexander Barth <alex@developmentseed.org> wrote:

Unfortunately, speed is an issue for our aggregation sites where
parsing time adds up accross all Drupal installations on the
server.

There are some good arguments to be made for decoupling parsing / aggregating directly within Drupal and moving it outside -- just putting nodes into Drupal.

I don't object to that SimplePie may well be the better
choice for a general use case - can we agree on a pluggable solution,
though?

Yes.

I can understand. But let's not desmiss the new aggregator solution as
Drupal 7 only material. A backport to 6 or even 5 could be very easy
to do. Moreover, it's pretty likely that Aron actually starts
developing the new aggregator on Drupal 5.

From a more personal point of view, I really would like to get rid of
leech and build on top of common ground as soon as possible - not only
when 7's out.

Hallelujah. So...if Morbus needs to move, can we start on the foundations of the one, true pluggable aggregation API of doom, together, now?


--
Boris Mann
Office 604-682-2889
Skype borismann
http://www.bryght.com