<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Syndication and accountability</title>
	<atom:link href="http://blog.jonudell.net/2008/01/15/syndication-and-accountability/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jonudell.net/2008/01/15/syndication-and-accountability/</link>
	<description>Strategies for Internet citizens</description>
	<lastBuildDate>Sun, 12 Feb 2012 18:22:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Michael R. Bernstein</title>
		<link>http://blog.jonudell.net/2008/01/15/syndication-and-accountability/#comment-122205</link>
		<dc:creator><![CDATA[Michael R. Bernstein]]></dc:creator>
		<pubDate>Thu, 17 Jan 2008 18:16:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/2008/01/15/syndication-and-accountability/#comment-122205</guid>
		<description><![CDATA[&quot;Note also that Jeff’s caveat about “which recipients of the original record need to be notified” implies owner-initiated push. But if the recipient is a subscriber, that update channel is already open and ready for use.&quot;

Hmm. We need to be clear on the division of responsibilities here: The owner is responsible for making notifications available, but the client is still responsible for initiating the retrieval.

I think Dave Winer observed once that most &#039;push&#039; architectures are actually &#039;scheduled pull&#039;, and that pretty much all successful architectures are pull-oriented, at least at the receiving edge.

&#039;Push&#039; only seems to work from the edge to the center (if there is one), or from the edge to the cloud (if there isn&#039;t).]]></description>
		<content:encoded><![CDATA[<p>&#8220;Note also that Jeff’s caveat about “which recipients of the original record need to be notified” implies owner-initiated push. But if the recipient is a subscriber, that update channel is already open and ready for use.&#8221;</p>
<p>Hmm. We need to be clear on the division of responsibilities here: The owner is responsible for making notifications available, but the client is still responsible for initiating the retrieval.</p>
<p>I think Dave Winer observed once that most &#8216;push&#8217; architectures are actually &#8216;scheduled pull&#8217;, and that pretty much all successful architectures are pull-oriented, at least at the receiving edge.</p>
<p>&#8216;Push&#8217; only seems to work from the edge to the center (if there is one), or from the edge to the cloud (if there isn&#8217;t).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stand</title>
		<link>http://blog.jonudell.net/2008/01/15/syndication-and-accountability/#comment-121660</link>
		<dc:creator><![CDATA[stand]]></dc:creator>
		<pubDate>Tue, 15 Jan 2008 19:56:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/2008/01/15/syndication-and-accountability/#comment-121660</guid>
		<description><![CDATA[Amen! It would save me a lot of heartache at work if I could get the &lt;a href=&quot;http://www.ihe.net&quot; rel=&quot;nofollow&quot;&gt;medical records people&lt;/a&gt; to understand this.]]></description>
		<content:encoded><![CDATA[<p>Amen! It would save me a lot of heartache at work if I could get the <a href="http://www.ihe.net" rel="nofollow">medical records people</a> to understand this.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

