Hey,
I wanted to point out a project that Doug sent me a link to yesterday:
http://tarekziade.wordpress.com/2008/08/20/atomisator-a-framework-to-build-custom-rss-feeds/
The project is focused around yahoo pipes style feed aggregation and
filtering, it's Python, GPL and it's spearheaded by Tarek Ziadé, the
author of the Expert Python Programming book you may have heard about
if you're subscribed to the TOPP Eng list -- http://tarekziade.wordpress.com/2008/08/08/a-new-python-book-expert-python-programming/
I think there are some very complementary ideas here. I know Ethan
has mentioned strict filtering as a desire in the past, and Randall
has hinted at some stuff that sounds like 'Enhancers' in the
Atomisator stack. We have virtually no trace of this sort of strict
filtering / mutating stack in the system presently, but I think it
could be a very interesting addition.
The first idea that pops into my head would be to try to use an
Atomisator filter stack as the driver of a mapping between items and
jugs, possibly bubbling some simple controls up. We currently don't
track what goes into each jug item by item -- it's all a ball of silly
queries at request time. I've been thinking lately about the need for
this sort of tracking anyway while investigating app engine and some
of it's query restrictions (plus I think it just makes a good deal of
logical sense).
It's not a huge priority or anything and I haven't really looked at
what this would mean in terms of a technical challenge. I doubt we're
very compatible currently, but even as an experiment, it looks like a
cool opportunity for cross pollination and possible mutual benefit.
- Luke
--
Archive:
http://www.openplans.org/projects/melkjug/lists/melkjug-development-list/archive/2008/08/1219328783482
To unsubscribe send an email with subject "unsubscribe" to [EMAIL PROTECTED]
Please contact [EMAIL PROTECTED] for questions.
