<?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: RESTful reliability continued&#8230;</title>
	<atom:link href="http://netzooid.com/blog/2007/03/25/restful-reliability-continued/feed/" rel="self" type="application/rss+xml" />
	<link>http://netzooid.com/blog/2007/03/25/restful-reliability-continued/</link>
	<description>gettin all zoidal on ya</description>
	<lastBuildDate>Sat, 24 Jul 2010 09:48:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Bill de hOra</title>
		<link>http://netzooid.com/blog/2007/03/25/restful-reliability-continued/comment-page-1/#comment-2389</link>
		<dc:creator>Bill de hOra</dc:creator>
		<pubDate>Sun, 08 Apr 2007 12:58:44 +0000</pubDate>
		<guid isPermaLink="false">http://netzooid.com/blog/2007/03/25/restful-reliability-continued/#comment-2389</guid>
		<description>ugly: yep, any reliable transmission over HTTP has to dela with its asymmetry - clients always initiate. The general theorem is that you need 5 steps to reach agreement  on  a transmission (and which can be compressed to 3). Physically on HTTP that maps to 2 requests. Models like BTF2.0 are perhaps more elegant, but require servers on either end. 

client unique ids: problem is trusting clients. This will work for controlled scenarios, not general purpose web. Aside from trusting them to generate something suitably  unique,  ids are a potential spam vector. I guess most enterprise messaging is controlled to some extent and will have out of band agreements in place.

Another option is to &quot;just dedup&quot; on the server. It will give protocol formalists heartburn, but it works if you&#039;re holding a long enough list of previously seen documents.</description>
		<content:encoded><![CDATA[<p>ugly: yep, any reliable transmission over HTTP has to dela with its asymmetry &#8211; clients always initiate. The general theorem is that you need 5 steps to reach agreement  on  a transmission (and which can be compressed to 3). Physically on HTTP that maps to 2 requests. Models like BTF2.0 are perhaps more elegant, but require servers on either end. </p>
<p>client unique ids: problem is trusting clients. This will work for controlled scenarios, not general purpose web. Aside from trusting them to generate something suitably  unique,  ids are a potential spam vector. I guess most enterprise messaging is controlled to some extent and will have out of band agreements in place.</p>
<p>Another option is to &#8220;just dedup&#8221; on the server. It will give protocol formalists heartburn, but it works if you&#8217;re holding a long enough list of previously seen documents.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Strachan</title>
		<link>http://netzooid.com/blog/2007/03/25/restful-reliability-continued/comment-page-1/#comment-2261</link>
		<dc:creator>James Strachan</dc:creator>
		<pubDate>Mon, 26 Mar 2007 08:57:27 +0000</pubDate>
		<guid isPermaLink="false">http://netzooid.com/blog/2007/03/25/restful-reliability-continued/#comment-2261</guid>
		<description>When a client is capable of generating a unique ID then that seems like the way to go...

http://www.goland.org/draft-goland-http-reliability-00.text</description>
		<content:encoded><![CDATA[<p>When a client is capable of generating a unique ID then that seems like the way to go&#8230;</p>
<p><a href="http://www.goland.org/draft-goland-http-reliability-00.text" rel="nofollow">http://www.goland.org/draft-goland-http-reliability-00.text</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

