<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: put</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/put.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2008-08-15T08:20:04+00:00</updated><author><name>Simon Willison</name></author><entry><title>REST, I just don't get it</title><link href="https://simonwillison.net/2008/Aug/15/katz/#atom-tag" rel="alternate"/><published>2008-08-15T08:20:04+00:00</published><updated>2008-08-15T08:20:04+00:00</updated><id>https://simonwillison.net/2008/Aug/15/katz/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://damienkatz.net/2008/08/rest-i-just-dont-get-it.html"&gt;REST, I just don&amp;#x27;t get it&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Read the comments for some excellent practical reasons to care about REST, including cache management (PUT and DELETE can expire the cache entries for the corresponding GET), the ability to add or move parts of the server API without redeploying client libraries and the idempotency of GET / PUT / DELETE and HEAD (repeated POST operations may have side-effects).


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/caching"&gt;caching&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/damien-katz"&gt;damien-katz&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/delete"&gt;delete&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/get"&gt;get&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/idempotency"&gt;idempotency&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/post"&gt;post&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/put"&gt;put&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/rest"&gt;rest&lt;/a&gt;&lt;/p&gt;



</summary><category term="caching"/><category term="damien-katz"/><category term="delete"/><category term="get"/><category term="idempotency"/><category term="post"/><category term="put"/><category term="rest"/></entry><entry><title>A Taxonomy of Event- and REST-based Comet</title><link href="https://simonwillison.net/2007/Nov/21/comet/#atom-tag" rel="alternate"/><published>2007-11-21T20:18:13+00:00</published><updated>2007-11-21T20:18:13+00:00</updated><id>https://simonwillison.net/2007/Nov/21/comet/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://cometdaily.com/2007/11/21/a-taxonomy-of-event-and-rest-based-comet/"&gt;A Taxonomy of Event- and REST-based Comet&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Kris Zyp describes a conceptual model for Comet messages based on REST semantics (so you can send a PUT referencing a specific URI down to a client to represent an idempotent state change).


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/comet"&gt;comet&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/http"&gt;http&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/idempotent"&gt;idempotent&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/javascript"&gt;javascript&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/kriszyp"&gt;kriszyp&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/put"&gt;put&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/rest"&gt;rest&lt;/a&gt;&lt;/p&gt;



</summary><category term="comet"/><category term="http"/><category term="idempotent"/><category term="javascript"/><category term="kriszyp"/><category term="put"/><category term="rest"/></entry></feed>