<?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: Ian Bicking on Atompub vs. WebDAV</title>
	<atom:link href="http://blog.mozilla.com/rob-sayre/2009/01/11/ian-bicking-on-atompub-vs-webdav/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mozilla.com/rob-sayre/2009/01/11/ian-bicking-on-atompub-vs-webdav/</link>
	<description>This Must Be the Place (Naive Melody)</description>
	<lastBuildDate>Thu, 10 Sep 2009 06:17:03 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ian Bicking</title>
		<link>http://blog.mozilla.com/rob-sayre/2009/01/11/ian-bicking-on-atompub-vs-webdav/comment-page-1/#comment-8892</link>
		<dc:creator>Ian Bicking</dc:creator>
		<pubDate>Mon, 12 Jan 2009 04:52:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/rob-sayre/?p=234#comment-8892</guid>
		<description>Hmm... yeah, I guess PUT would work fine.  It&#039;d be less closely related to Atompub then, but that&#039;s kind of incidental.  Also, everywhere else where you PUT an entry it isn&#039;t directly related to the rendered page (it&#039;s specified explicitly in the atom entry using a link).  If you PUT to its final destination it&#039;s hard to apply to an existing application.  Except for that PUT you could take an existing CMS and tweak a few things in the template, and install a parallel component that handles this API, in a completely separate URL space.</description>
		<content:encoded><![CDATA[<p>Hmm&#8230; yeah, I guess PUT would work fine.  It&#8217;d be less closely related to Atompub then, but that&#8217;s kind of incidental.  Also, everywhere else where you PUT an entry it isn&#8217;t directly related to the rendered page (it&#8217;s specified explicitly in the atom entry using a link).  If you PUT to its final destination it&#8217;s hard to apply to an existing application.  Except for that PUT you could take an existing CMS and tweak a few things in the template, and install a parallel component that handles this API, in a completely separate URL space.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
