<?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: PATCH the message</title>
	<atom:link href="http://www.markbaker.ca/blog/2008/02/patch-the-message/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.markbaker.ca/blog/2008/02/patch-the-message/</link>
	<description>Celebrating the power of the Web</description>
	<lastBuildDate>Fri, 26 Aug 2011 20:00:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Mark Baker</title>
		<link>http://www.markbaker.ca/blog/2008/02/patch-the-message/comment-page-1/#comment-331</link>
		<dc:creator>Mark Baker</dc:creator>
		<pubDate>Wed, 20 Feb 2008 06:11:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.markbaker.ca/blog/2008/02/16/patch-the-message/#comment-331</guid>
		<description>Yah, good question Mark.  I actually gave this some thought during the discussions.  What I realized was that PATCH is only (well, modulo the use of data-format specific diff formats that are aware of semantically meaningless changes) an optimized PUT in the case where strong etags are used (and If-Match on the PATCH request of course).  Beyond that, it provides weaker guarantees about the terminal state of the resource and therefore isn&#039;t just an optimized PUT.</description>
		<content:encoded><![CDATA[<p>Yah, good question Mark.  I actually gave this some thought during the discussions.  What I realized was that PATCH is only (well, modulo the use of data-format specific diff formats that are aware of semantically meaningless changes) an optimized PUT in the case where strong etags are used (and If-Match on the PATCH request of course).  Beyond that, it provides weaker guarantees about the terminal state of the resource and therefore isn&#8217;t just an optimized PUT.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Nottingham</title>
		<link>http://www.markbaker.ca/blog/2008/02/patch-the-message/comment-page-1/#comment-330</link>
		<dc:creator>Mark Nottingham</dc:creator>
		<pubDate>Sat, 16 Feb 2008 16:08:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.markbaker.ca/blog/2008/02/16/patch-the-message/#comment-330</guid>
		<description>Right. The interesting question, to me, is whether client-side toolkits will evolve to the point where they&#039;re smart enough to realise that they should PATCH when the user says to PUT -- and whether that&#039;ll be considered a feature or a bug.

Given the state of client-side toolkits today, though, I think we&#039;re in for a long-ish wait before we get a good answer.</description>
		<content:encoded><![CDATA[<p>Right. The interesting question, to me, is whether client-side toolkits will evolve to the point where they&#8217;re smart enough to realise that they should PATCH when the user says to PUT &#8212; and whether that&#8217;ll be considered a feature or a bug.</p>
<p>Given the state of client-side toolkits today, though, I think we&#8217;re in for a long-ish wait before we get a good answer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam Ruby</title>
		<link>http://www.markbaker.ca/blog/2008/02/patch-the-message/comment-page-1/#comment-329</link>
		<dc:creator>Sam Ruby</dc:creator>
		<pubDate>Sat, 16 Feb 2008 14:20:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.markbaker.ca/blog/2008/02/16/patch-the-message/#comment-329</guid>
		<description>s/says/will say/ and... well, DUH!  :-)</description>
		<content:encoded><![CDATA[<p>s/says/will say/ and&#8230; well, DUH!  :-)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

