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