On Monday 26 November 2007, Andrew
Gwozdziewycz wrote:
Sure. If you aren't worried about
keeping a history of all posts from
this point on, a simple solution would
be to download each feed and
serve it from your own webserver.
(snip)
My django solution, involves a similar
thing, but it adds each feed
item to a database table and the list
of feeds is also in the
database. Feeds can be managed from the
admin interface provided by
django and they are assembled on each
request for them.
I may be misunderstanding that, but I was
thinking of a cache that archives
the *entire* feed, not just the last n
entries.
Say the site has a feed with the latest
10 entries in it. The
cache pulls
down all 10. Some time later, the feed is
checked again. The cache
should
not replace the 10 existing entries with
the 10 new entries, but instead add
any new entries to the existing ones. That way, another device can
pull,
say, the last 100 (or even 1000) entries
from the cache.