<?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: What is REST?</title>
	<atom:link href="http://sarahtaraporewalla.com/thoughts/design/what-is-rest/feed/" rel="self" type="application/rss+xml" />
	<link>http://sarahtaraporewalla.com/thoughts/design/what-is-rest/</link>
	<description></description>
	<lastBuildDate>Tue, 08 Jun 2010 10:50:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Sarah</title>
		<link>http://sarahtaraporewalla.com/thoughts/design/what-is-rest/comment-page-1/#comment-924</link>
		<dc:creator>Sarah</dc:creator>
		<pubDate>Thu, 02 Apr 2009 22:08:47 +0000</pubDate>
		<guid isPermaLink="false">http://sarahtaraporewalla.com/thoughts/?p=159#comment-924</guid>
		<description>While a lot of people tend to make a PUT request update a whole object, the HTTP protocol does not enforce this. The server, at all times, holds authority as to what is updated. 

I choose to take Roy Fielding&#039;s definition as the definitive version, given his contributions to HTTP and REST. His opinion is : 
FWIW, PUT does not mean store.  I must have repeated that a million
times in webdav and related lists.  HTTP defines the intended
semantics of the communication -- the expectations of each party.

The protocol does not define how either side fulfills those expectations,

and it makes damn sure it doesn&#039;t prevent a server from having
absolute authority over its own resources.  Also, resources are
known to change over time, so if a server accepts an invalid Atom
entry via PUT one second and then immediately thereafter decides
to change it to a valid entry for later GETs, life is grand. http://www.imc.org/atom-protocol/mail-archive/msg05425.html</description>
		<content:encoded><![CDATA[<p>While a lot of people tend to make a PUT request update a whole object, the HTTP protocol does not enforce this. The server, at all times, holds authority as to what is updated. </p>
<p>I choose to take Roy Fielding&#8217;s definition as the definitive version, given his contributions to HTTP and REST. His opinion is :<br />
FWIW, PUT does not mean store.  I must have repeated that a million<br />
times in webdav and related lists.  HTTP defines the intended<br />
semantics of the communication &#8212; the expectations of each party.</p>
<p>The protocol does not define how either side fulfills those expectations,</p>
<p>and it makes damn sure it doesn&#8217;t prevent a server from having<br />
absolute authority over its own resources.  Also, resources are<br />
known to change over time, so if a server accepts an invalid Atom<br />
entry via PUT one second and then immediately thereafter decides<br />
to change it to a valid entry for later GETs, life is grand. <a href="http://www.imc.org/atom-protocol/mail-archive/msg05425.html" rel="nofollow">http://www.imc.org/atom-protocol/mail-archive/msg05425.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Leishman</title>
		<link>http://sarahtaraporewalla.com/thoughts/design/what-is-rest/comment-page-1/#comment-889</link>
		<dc:creator>Chris Leishman</dc:creator>
		<pubDate>Tue, 31 Mar 2009 11:53:00 +0000</pubDate>
		<guid isPermaLink="false">http://sarahtaraporewalla.com/thoughts/?p=159#comment-889</guid>
		<description>I think, in your &quot;Representations&quot; section, you mean to say &quot;the message sent by PUT needs specify only parts of the object&quot;.

POST is about sending a message to a resource.  PUT is about updating the resource itself.</description>
		<content:encoded><![CDATA[<p>I think, in your &#8220;Representations&#8221; section, you mean to say &#8220;the message sent by PUT needs specify only parts of the object&#8221;.</p>
<p>POST is about sending a message to a resource.  PUT is about updating the resource itself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clinton Begin</title>
		<link>http://sarahtaraporewalla.com/thoughts/design/what-is-rest/comment-page-1/#comment-825</link>
		<dc:creator>Clinton Begin</dc:creator>
		<pubDate>Thu, 26 Mar 2009 18:12:05 +0000</pubDate>
		<guid isPermaLink="false">http://sarahtaraporewalla.com/thoughts/?p=159#comment-825</guid>
		<description>However you define it, &#039;rest&#039; is something good software developers don&#039;t get enough of!</description>
		<content:encoded><![CDATA[<p>However you define it, &#8216;rest&#8217; is something good software developers don&#8217;t get enough of!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
