[http://creativecommons.org/licenses/by/3.0/]
This work is licensed under a CC
Attribution 3.0 Unported License [http://creativecommons.org/licenses/by/3.0/]
Feeds are useful as information sources adhering to a standardized format, but they usually have a single source. In a larger picture of information flows on the Web, the question is how feeds can be handled more efficiently and flexibly. This includes questions such as load balancing and user statistics, but also more complex scenarios such as aggregating (and maybe even filtering) feeds. Since feeds use a standardized data format, such repurposed information again can be published as a feed, creating a flexible architecture of feed-based information dissemination, allowing an arbitrary number of feed aggregation steps.
XMLHttpRequest
gets into the way<link rel="alternate" type="application/rdf+xml" title="…" href="…" /> <link rel="alternate" type="application/rss+xml" title="…" href="…" />
<link rel="alternate" type="application/atom+xml" title="…" href="…" />
joint tag feedis as simple as aggregating feeds
<table> <thead> <tr> <th>Feed Roll</th> <th>Feed Items</th> </tr> </thead> <tbody> <tr> <td valign="top"> <script type="text/javascript" src="http://www.google.com/reader/ui/publisher-en.js"></script> <script type="text/javascript" src="http://www.google.com/reader/public/javascript-sub/user/16601496766743088901/label/delicious REST?callback=GRC_p(%7Bc%3A%22gray%22%2Ct%3A%22My%20%5C%22delicious%20REST%5C%22%20Feed%20Roll%22%2Cb%3A%22true%22%7D)%3Bnew%20GRC"></script> </td> <td valign="top"> <script type="text/javascript" src="http://www.google.com/reader/ui/publisher-en.js"></script> <script type="text/javascript" src="http://www.google.com/reader/public/javascript/user/16601496766743088901/label/delicious REST?n=10&callback=GRC_p(%7Bc%3A%22gray%22%2Ct%3A%22%5C%22delicious%20REST%5C%22%20via%20dret%22%2Cs%3A%22true%22%2Cb%3A%22false%22%7D)%3Bnew%20GRC"></script> </td> </tr> </thead> </table>
things