[development] Core feed publishing
agentrickard at gmail.com
Wed Jul 4 18:40:57 UTC 2007
There are a number of people already working in the direction you propose,
and we'd love to have you join in.
Core aggregator is totally separate from the node system, so I don't
understand where you are coming from.
I'd encourage you to join http://groups.drupal.org/rss-aggregation if you
are not already a member. We are trying to coordinate efforts in this corner
We especially need reviewers for Aron Novak's Summer of Code work.
http://groups.drupal.org/node/4624 and related.
Aron's work is targeted as contrib for Drupal 5 & 6, with application for
core in Drupal 7.
In particular, take a look at the proposed API, which has been in the works
since the last DrupalCon. http://groups.drupal.org/node/3528 and is
foundational to Aron's work.
- Ken Rickard
Date: Mon, 2 Jul 2007 23:02:14 -0400
From: beerfan <beerfan at gmail.com>
Subject: [development] Core feed publishing
To: drupal-devel at drupal.org
<8de7f7140707022002ya99539fg711d32e052f63cb5 at mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Feed publishing, and the RSS format in particular, is currently
tightly coupled with the node module. Because of this supporting Atom
or extending feed functionality with custom modules isn't as clean as
it should be. For example, adding a name-space to a node feed requires
replacing default feeds with custom feeds instead of simply "theming"
the output of feeds as you would do with every other form of content
display. Publishing only Atom feeds (and disabling RSS) is impossible.
I would like to see feed publishing become more generic and more
extensible in the core and I believe there has been discussion around
this in the past.
Ideally, feed publishing would be a generic module or api which would
support the following needs.
1. Multiple arbitrary feed formats (RSS, Atom) with a default
2. Custom name-spaces and elements (possibly via themes or hooks)
3. Publish comment feeds or any other arbitrary content (watchdog
events, users, etc.)
4. The ability to provide a feed of any arbitrary set of content
(e.g., view, node-queue)
5. Optimize publishing for very high traffic feeds (e.g., caching or
saving as static xml file)
6. The ability to disable feeds
It is currently possibly to cobble together most of the above
functionality with views.module, commentrss.module, and atom.module
but the solution is sub-optimal for many reasons.
I recently started creating a feed.module against HEAD with the hope
that it could turn into a core module which would make feed publishing
more flexible and collect all feed formatting and publishing code and
eliminate the RSS publishing functionality in node.module. However,
since 6.x was just frozen there's probably no hope of introducing this
now but I'd still like to re-float the idea and get some feedback. In
particular, I'm curious if anyone else is already working on such a
project, if there are any side-effects of separating feed publishing
from node.module that I haven't considered, or if this problem might
be better approached using views as the complete solution (not really
viable since views is not a core module). Please ignore the fact that
this can't be implemented for 6.x.
As an example of an issue I have faced, feedburner.com adds a "number
of comments for this entry" if the feed includes the "wfw:commentsRss"
element pointing to the comment feed for the entry. I have modified
the commentrss.module to add the element to the node feed but there is
no way to add the "wfw" name-space to the node feed without replacing
it with a custom feed so I had to add the name-space to each instance
of the "commentRss" element.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the development