<?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: links for 2008-01-22</title>
	<atom:link href="http://marketingtechblog.com/2008/01/22/links-for-2008-01-22/feed/" rel="self" type="application/rss+xml" />
	<link>http://marketingtechblog.com/2008/01/22/links-for-2008-01-22/</link>
	<description>new media strategies and other marketing gems</description>
	<pubDate>Sat, 10 Jan 2009 00:34:37 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mike Schinkel</title>
		<link>http://marketingtechblog.com/2008/01/22/links-for-2008-01-22/comment-page-1/#comment-79507</link>
		<dc:creator>Mike Schinkel</dc:creator>
		<pubDate>Thu, 24 Jan 2008 05:31:26 +0000</pubDate>
		<guid isPermaLink="false">http://marketingtechblog.com/2008/01/22/links-for-2008-01-22/#comment-79507</guid>
		<description>Oh, and in case anyone thinks "&lt;i&gt;GET must be safe&lt;/i&gt;" is just standardista mumbo-jumbo and it doesn't really matter, realize that is what a lot of people thought until the Google Web Accellerator fiasco.  Here are some links:

-- http://blog.moertel.com/articles/2005/10/25/google-web-accelerator-vs-unsafe-linking-round-two
-- http://bitworking.org/news/I_m_sorry__I_can_t_kiss_it_and_make_it_better_
-- http://37signals.com/svn/archives2/google_web_accelerator_hey_not_so_fast_an_alert_for_web_app_designers.php

Also I'd highly recommend anyone wanting to design an API to discuss the best way to provide a RESTful API on the rest-discuss mailing list:

-- http://tech.groups.yahoo.com/group/rest-discuss/</description>
		<content:encoded><![CDATA[<div class="KonaBody">Oh, and in case anyone thinks &#8220;<i>GET must be safe</i>&#8221; is just standardista mumbo-jumbo and it doesn&#8217;t really matter, realize that is what a lot of people thought until the Google Web Accellerator fiasco.  Here are some links:</p>
<p>&#8211; <a href="http://blog.moertel.com/articles/2005/10/25/google-web-accelerator-vs-unsafe-linking-round-two" rel="nofollow">http://blog.moertel.com/articles/2005/10/25/google-web-accelerator-vs-unsafe-linking-round-two</a><br />
&#8211; <a href="http://bitworking.org/news/I_m_sorry__I_can_t_kiss_it_and_make_it_better_" rel="nofollow">http://bitworking.org/news/I_m_sorry__I_can_t_kiss_it_and_make_it_better_</a><br />
&#8211; <a href="http://37signals.com/svn/archives2/google_web_accelerator_hey_not_so_fast_an_alert_for_web_app_designers.php" rel="nofollow">http://37signals.com/svn/archives2/google_web_accelerator_hey_not_so_fast_an_alert_for_web_app_designers.php</a></p>
<p>Also I&#8217;d highly recommend anyone wanting to design an API to discuss the best way to provide a RESTful API on the rest-discuss mailing list:</p>
<p>&#8211; <a href="http://tech.groups.yahoo.com/group/rest-discuss/" rel="nofollow">http://tech.groups.yahoo.com/group/rest-discuss/</a></div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Schinkel</title>
		<link>http://marketingtechblog.com/2008/01/22/links-for-2008-01-22/comment-page-1/#comment-79505</link>
		<dc:creator>Mike Schinkel</dc:creator>
		<pubDate>Thu, 24 Jan 2008 05:08:36 +0000</pubDate>
		<guid isPermaLink="false">http://marketingtechblog.com/2008/01/22/links-for-2008-01-22/#comment-79505</guid>
		<description>Snipr's API is cool, until you realize that it violates a principle tenet of web architecture; GETs should be "safe" (have no side effects.)  See &lt;a href="http://www.w3.org/2001/tag/doc/whenToUseGet#safe" rel="nofollow"&gt;W3C's TAG Finding "When to use GET"&lt;/a&gt; which states "&lt;i&gt;GET is used for safe interactions and SHOULD NOT have the significance of taking an action other than retrieval.&lt;/i&gt;"

Several more references:

-- http://www.w3.org/DesignIssues/Axioms#state
-- http://www.intertwingly.net/blog/784.html
-- http://www.cs.tut.fi/~jkorpela/forms/methods.html
-- http://lists.w3.org/Archives/Public/www-tag/2002Apr/0091.html</description>
		<content:encoded><![CDATA[<div class="KonaBody">Snipr&#8217;s API is cool, until you realize that it violates a principle tenet of web architecture; GETs should be &#8220;safe&#8221; (have no side effects.)  See <a href="http://www.w3.org/2001/tag/doc/whenToUseGet#safe" rel="nofollow">W3C&#8217;s TAG Finding &#8220;When to use GET&#8221;</a> which states &#8220;<i>GET is used for safe interactions and SHOULD NOT have the significance of taking an action other than retrieval.</i>&#8221;</p>
<p>Several more references:</p>
<p>&#8211; <a href="http://www.w3.org/DesignIssues/Axioms#state" rel="nofollow">http://www.w3.org/DesignIssues/Axioms#state</a><br />
&#8211; <a href="http://www.intertwingly.net/blog/784.html" rel="nofollow">http://www.intertwingly.net/blog/784.html</a><br />
&#8211; <a href="http://www.cs.tut.fi/~jkorpela/forms/methods.html" rel="nofollow">http://www.cs.tut.fi/~jkorpela/forms/methods.html</a><br />
&#8211; <a href="http://lists.w3.org/Archives/Public/www-tag/2002Apr/0091.html" rel="nofollow">http://lists.w3.org/Archives/Public/www-tag/2002Apr/0091.html</a></div>
]]></content:encoded>
	</item>
</channel>
</rss>
