<?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: Optimistic Concurrency &#8211; Where is your merge code?</title>
	<atom:link href="http://torrez.us/archives/2006/08/04/477/feed/" rel="self" type="application/rss+xml" />
	<link>http://torrez.us/archives/2006/08/04/477/</link>
	<description>Hi.</description>
	<lastBuildDate>Fri, 02 Mar 2012 05:57:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Scott Lamb</title>
		<link>http://torrez.us/archives/2006/08/04/477/comment-page-1/#comment-13579</link>
		<dc:creator>Scott Lamb</dc:creator>
		<pubDate>Fri, 25 Aug 2006 01:22:01 +0000</pubDate>
		<guid isPermaLink="false">http://torrez.us/archives/2006/08/04/477/#comment-13579</guid>
		<description>&quot;Exploding on conflicts&quot; is not a horrible choice for small web forms. It&#039;s really, really easy to write and lets whoever made the most recent change know that they should retry. (Assume they either have short-term memory or you help them out by sending back the form elements.) Not much work is lost.

On the other hand, silently overwriting is what happens without any concurrent control at all. If you call that half-baked OCC...well, I think there&#039;s about half an implementation that you can delete without losing functionality. Better to add the other half, though, because this behavior is horrible. It potentially loses lots of work without ever telling anyone.

Now, when you talk about web services...that may be different. If there&#039;s a lot of information submitted in one shot and the human is farther away, you&#039;ll have to be smarter in your merging.</description>
		<content:encoded><![CDATA[&#8220;Exploding on conflicts&#8221; is not a horrible choice for small web forms. It&#8217;s really, really easy to write and lets whoever made the most recent change know that they should retry. (Assume they either have short-term memory or you help them out by sending back the form elements.) Not much work is lost.<br />
<br />
On the other hand, silently overwriting is what happens without any concurrent control at all. If you call that half-baked OCC&#8230;well, I think there&#8217;s about half an implementation that you can delete without losing functionality. Better to add the other half, though, because this behavior is horrible. It potentially loses lots of work without ever telling anyone.<br />
<br />
Now, when you talk about web services&#8230;that may be different. If there&#8217;s a lot of information submitted in one shot and the human is farther away, you&#8217;ll have to be smarter in your merging.]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon Smith &#187; Atom and Optimistic Concurrency</title>
		<link>http://torrez.us/archives/2006/08/04/477/comment-page-1/#comment-11890</link>
		<dc:creator>Brandon Smith &#187; Atom and Optimistic Concurrency</dc:creator>
		<pubDate>Mon, 07 Aug 2006 12:24:47 +0000</pubDate>
		<guid isPermaLink="false">http://torrez.us/archives/2006/08/04/477/#comment-11890</guid>
		<description>[...] Elias Torres » Blog Archive » Optimistic Concurrency - Where is your merge code? [...]</description>
		<content:encoded><![CDATA[[...] Elias Torres » Blog Archive » Optimistic Concurrency &#8211; Where is your merge code? [...]]]></content:encoded>
	</item>
	<item>
		<title>By: snellspace.com &#187; Blog Archive &#187; Optimistic Cheese</title>
		<link>http://torrez.us/archives/2006/08/04/477/comment-page-1/#comment-11704</link>
		<dc:creator>snellspace.com &#187; Blog Archive &#187; Optimistic Cheese</dc:creator>
		<pubDate>Fri, 04 Aug 2006 16:14:41 +0000</pubDate>
		<guid isPermaLink="false">http://torrez.us/archives/2006/08/04/477/#comment-11704</guid>
		<description>[...] Elias: &#8220;Queso now implements [Optimistic Concurrency] too&#8221; [...]</description>
		<content:encoded><![CDATA[[...] Elias: &#8220;Queso now implements [Optimistic Concurrency] too&#8221; [...]]]></content:encoded>
	</item>
</channel>
</rss>

