<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Interoperability and Service Cascading</title>
	<atom:link href="http://itredux.com/2006/01/24/interoperability-and-service-cascading/feed/" rel="self" type="application/rss+xml" />
	<link>http://itredux.com/2006/01/24/interoperability-and-service-cascading/</link>
	<description>New Rules for a New IT World</description>
	<pubDate>Wed, 03 Dec 2008 23:10:37 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7-beta3</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: IT&#124;Redux</title>
		<link>http://itredux.com/2006/01/24/interoperability-and-service-cascading/comment-page-1/#comment-45666</link>
		<dc:creator>IT&#124;Redux</dc:creator>
		<pubDate>Mon, 12 Feb 2007 05:50:10 +0000</pubDate>
		<guid isPermaLink="false">http://itredux.com/blog/2006/01/24/interoperability-and-service-cascading/#comment-45666</guid>
		<description>[...] This little experiement taught me a couple of things: First, service cascading works, and we should thank standards such as RSS for it. Second, using a third-party service to fetch hundreds of feed and aggregate thousands of entries while caching the results for you is not a bad idea, especially if you&#8217;re running your blog from a single server. Third, Yahoo! Pipes works, but its capabilities are fairly limited so far, and sorting does not work at all, which is a shame really. I very much look forward to the next revision, which hopefully will let me connect from Dabble DB directly in order to automatically import the list of feeds that I want to aggregate. In the meantime, have fun with this stream of unfiltered Office 2.0 News. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] This little experiement taught me a couple of things: First, service cascading works, and we should thank standards such as <span class="caps">RSS</span> for it. Second, using a third-party service to fetch hundreds of feed and aggregate thousands of entries while caching the results for you is not a bad idea, especially if you&#8217;re running your blog from a single server. Third, Yahoo! Pipes works, but its capabilities are fairly limited so far, and sorting does not work at all, which is a shame really. I very much look forward to the next revision, which hopefully will let me connect from Dabble <span class="caps">DB</span> directly in order to automatically import the list of feeds that I want to aggregate. In the meantime, have fun with this stream of unfiltered Office 2.0 News.&nbsp;[&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: IT&#124;Redux</title>
		<link>http://itredux.com/2006/01/24/interoperability-and-service-cascading/comment-page-1/#comment-356</link>
		<dc:creator>IT&#124;Redux</dc:creator>
		<pubDate>Sun, 12 Feb 2006 16:41:21 +0000</pubDate>
		<guid isPermaLink="false">http://itredux.com/blog/2006/01/24/interoperability-and-service-cascading/#comment-356</guid>
		<description>[...] Most social bookmarking tools have the same problem: they cannot sustain the growth of their user base and have to work in batch mode. What this means is that if you update your bookmarks stored in del.ico.us, changes might be reflected only 24 hours later. Similar problems plague Simpy and FeedDigest, which makes service cascading less reliable than it could be. Nevertheless, both services are currently being improved and I would expect these problems to be resolved no later than in the second half of 2006. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Most social bookmarking tools have the same problem: they cannot sustain the growth of their user base and have to work in batch mode. What this means is that if you update your bookmarks stored in del.ico.us, changes might be reflected only 24 hours later. Similar problems plague Simpy and FeedDigest, which makes service cascading less reliable than it could be. Nevertheless, both services are currently being improved and I would expect these problems to be resolved no later than in the second half of 2006.&nbsp;[&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: IT&#124;Redux</title>
		<link>http://itredux.com/2006/01/24/interoperability-and-service-cascading/comment-page-1/#comment-343</link>
		<dc:creator>IT&#124;Redux</dc:creator>
		<pubDate>Sun, 12 Feb 2006 04:29:33 +0000</pubDate>
		<guid isPermaLink="false">http://itredux.com/blog/2006/01/24/interoperability-and-service-cascading/#comment-343</guid>
		<description>[...] Most blog authors like to syndicate the content of other blogs, or display some information that is published through public feeds, such as bookmarks, calendar events, or pictures. When you need to process such feeds for creating digests, re-ordering entries, or generating a snipet of JavaScript code that will display on your blog the content you&#8217;re getting from others, a service such as FeedDigest becomes very useful. It can also be used for cascading multiple services without having to write any code. A free account lets you produce five digest, but it will cost you $49.99 a year if you need up to 50. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Most blog authors like to syndicate the content of other blogs, or display some information that is published through public feeds, such as bookmarks, calendar events, or pictures. When you need to process such feeds for creating digests, re-ordering entries, or generating a snipet of JavaScript code that will display on your blog the content you&#8217;re getting from others, a service such as FeedDigest becomes very useful. It can also be used for cascading multiple services without having to write any code. A free account lets you produce five digest, but it will cost you $49.99 a year if you need up to 50.&nbsp;[&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: IT&#124;Redux</title>
		<link>http://itredux.com/2006/01/24/interoperability-and-service-cascading/comment-page-1/#comment-181</link>
		<dc:creator>IT&#124;Redux</dc:creator>
		<pubDate>Wed, 25 Jan 2006 20:10:18 +0000</pubDate>
		<guid isPermaLink="false">http://itredux.com/blog/2006/01/24/interoperability-and-service-cascading/#comment-181</guid>
		<description>[...] Beyond peer-to-peer collaboration, syndication opens the door to social cooperation. This really is the essence of Web 2.0, and Office 2.0 should benefit from it as much as possible. Syndication also provides the mechanisms that are required for integrating multiple services with each other, as described in this recent article. As a result, services that offer RSS feeds and REST APIs always get my vote over ones that do not. Hint to LinkedIn: this is where I believe the most significant improvements could be made to your exceptional service. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Beyond peer-to-peer collaboration, syndication opens the door to social cooperation. This really is the essence of Web 2.0, and Office 2.0 should benefit from it as much as possible. Syndication also provides the mechanisms that are required for integrating multiple services with each other, as described in this recent article. As a result, services that offer <span class="caps">RSS</span> feeds and <span class="caps">REST</span> APIs always get my vote over ones that do not. Hint to LinkedIn: this is where I believe the most significant improvements could be made to your exceptional service.&nbsp;[&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Cooper</title>
		<link>http://itredux.com/2006/01/24/interoperability-and-service-cascading/comment-page-1/#comment-177</link>
		<dc:creator>Peter Cooper</dc:creator>
		<pubDate>Wed, 25 Jan 2006 18:38:23 +0000</pubDate>
		<guid isPermaLink="false">http://itredux.com/blog/2006/01/24/interoperability-and-service-cascading/#comment-177</guid>
		<description>We're adding some interesting new features to reduce that point of failure. We've seen with FeedBurner and other services that people don't really like single points of failure, and we've figured out a great way around it. More details to come... :)</description>
		<content:encoded><![CDATA[<p>We&#8217;re adding some interesting new features to reduce that point of failure. We&#8217;ve seen with FeedBurner and other services that people don&#8217;t really like single points of failure, and we&#8217;ve figured out a great way around it. More details to come&#8230;&nbsp;:)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
