Good catch, it used to do that in maybe_save, so the right spot to do
that now might be the composite controller save method? I had it there
mainly to catch feeds that have never been seen by the system at all
-- it basically extracted new feeds in the configuration and passed
those along to keep it lightweight for now.
http://trac.openplans.org/melkjug/changeset/1108/melkjug/trunk/melkjug/controllers/reader.py
I think in the future we could give more thorough hints to the
backend, but that's a different ball of wax.
- Luke
On Jul 23, 2008, at 12:43 AM, [EMAIL PROTECTED] wrote:
Author: rleeds
Date: 2008-07-23 00:43:14 -0400 (Wed, 23 Jul 2008)
New Revision: 1118
Modified:
melkjug/trunk/melkjug/controllers/reader.py
Log:
Accidently deleted a fetch request a while back.
Modified: melkjug/trunk/melkjug/controllers/reader.py
===================================================================
--- melkjug/trunk/melkjug/controllers/reader.py 2008-07-22 22:03:53
UTC (rev 1117)
+++ melkjug/trunk/melkjug/controllers/reader.py 2008-07-23 04:43:14
UTC (rev 1118)
@@ -82,6 +82,8 @@
# a bit of validation here could be good...
count = 15
+
+ backend.consider_fetching(mixing_spec.feeds)
# get 'em...
items = choose_items(mixing_spec, count=count,
user=self.current_user)
--
To unsubscribe send an email with subject "unsubscribe" to [EMAIL PROTECTED]
. Please contact [EMAIL PROTECTED]
for questions.
--
Archive:
http://www.openplans.org/projects/melkjug/lists/melkjug-development-list/archive/2008/07/1216824739080
To unsubscribe send an email with subject "unsubscribe" to [EMAIL PROTECTED]
Please contact [EMAIL PROTECTED] for questions.
