Aggregator2 / Podcast Aggregator

I'm implementing a podcast aggregator and I'm working with
Agg2.  I was 
going to modify aggregator2_parse_items() to pull the
<ENCLOSURE> (which 
contains the podcast mp3 or whatever) and other fields out
of the RSS 
feed and add them to the agg2_item type.  But I feel that
the following 
might be a better solution and would like some feedback.

Would it be worthwhile to add an invoke_all call for
'_parse_items' and 
pass the $items to that when parsing new RSS items?  This
would allow 
other modules to react when agg2 does an update as at the
nodeapi level, 
you can't access any info that was in the RSS feed that
agg2 isn't 
already sending to the database.

Thanks for any input.

-- 

Rob Roy Barreca
Electronic Insight Corporation
12526 High Bluff Drive, Suite 300
San Diego, CA 92130
http://www.electroni
cinsight.com
robelectronicinsight.com

Hmmm...think I might just need to use the prepare nodeapi
hook and I'll 
be golden.

Rob Roy Barreca
Electronic Insight Corporation
12526 High Bluff Drive, Suite 300
San Diego, CA 92130
http://www.electroni
cinsight.com
robelectronicinsight.com



Rob Barreca wrote:
> I'm implementing a podcast aggregator and I'm working
with Agg2.  I 
> was going to modify aggregator2_parse_items() to pull
the <ENCLOSURE> 
> (which contains the podcast mp3 or whatever) and other
fields out of 
> the RSS feed and add them to the agg2_item type.  But I
feel that the 
> following might be a better solution and would like
some feedback.
>
> Would it be worthwhile to add an invoke_all call for
'_parse_items' 
> and pass the $items to that when parsing new RSS items?
 This would 
> allow other modules to react when agg2 does an update
as at the 
> nodeapi level, you can't access any info that was in
the RSS feed that 
> agg2 isn't already sending to the database.
>
> Thanks for any input.
>

On 25-Apr-06, at 12:42 PM, Rob Barreca wrote:

> I'm implementing a podcast aggregator and I'm working
with Agg2.  I  
> was going to modify aggregator2_parse_items() to pull
the  
> <ENCLOSURE> (which contains the podcast mp3 or
whatever) and other  
> fields out of the RSS feed and add them to the
agg2_item type.  But  
> I feel that the following might be a better solution
and would like  
> some feedback.
>
> Would it be worthwhile to add an invoke_all call for
'_parse_items'  
> and pass the $items to that when parsing new RSS items?
 This would  
> allow other modules to react when agg2 does an update
as at the  
> nodeapi level, you can't access any info that was in
the RSS feed  
> that agg2 isn't already sending to the database.

username "budda" was doing a new project --
check cvs.drupal.org for  
aggregator_node or something like that. It uses the core
aggregator  
to manage all feeds etc., and then just links them to node
types.  
It's an interesting approach.

-- Boris

Op woensdag 26 april 2006 19:31, schreef Boris Mann:
> username "budda" was doing a new project --
check cvs.drupal.org for  
> aggregator_node or something like that. It uses the
core aggregator  
> to manage all feeds etc., and then just links them to
node types.  
> It's an interesting approach.

There is also *still* node aggregator. It works for 4.6 and
we are getting it 
ready for 4.7. 
Budda and I decided to team up and develop a central,
general 
feedparser.module API. 

I would love to see more people involved, because we would
like to make this 
THE central feed parsing library over time.
 
h
ttp://cvs.drupal.org/viewcvs/drupal/contributions/modules/fe
edparser/feedparser.module?rev=1.3&view=markup 

Bčr

-- 
| Bčr Kessels | webschuur.com | website development |
| Jabber & Google Talk: berjabber.webschuur.com
| http://bler.webschuur.com | http://www.webschuur.com
|


Heeft het gebruik van Sympal gevolgen voor de
eigendomsrechten van het 
gepubliceerde materiaal?:
 
http://help.sympal.nl/heeft_het_gebruik_van_sympal_gevol
gen_voor_de_eigendomsrechten_van_het_gepubliceerde_materiaal