<?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: The Hidden Danger of Synchronization</title>
	<atom:link href="http://www.hawksley.net/2009/02/the-hidden-danger-of-synchronization/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hawksley.net/2009/02/the-hidden-danger-of-synchronization/</link>
	<description>John Hawksley &#124; www.hawksley.net</description>
	<lastBuildDate>Wed, 06 May 2009 13:20:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: John</title>
		<link>http://www.hawksley.net/2009/02/the-hidden-danger-of-synchronization/comment-page-1/#comment-9</link>
		<dc:creator>John</dc:creator>
		<pubDate>Mon, 23 Feb 2009 06:56:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawksley.net/?p=48#comment-9</guid>
		<description>Exactly, and they can be very useful if you&#039;re doing Object.Wait()/.Notify() semaphores (which bring their own special class of problems). Debugging them ranges from impossible (if they&#039;re suspected) to hard (if you have a stack trace of one actually happening).  At least in the newer JVMs the deadlock detector will actually point out the participants in a deadlock right there in the trace.</description>
		<content:encoded><![CDATA[<p>Exactly, and they can be very useful if you&#8217;re doing Object.Wait()/.Notify() semaphores (which bring their own special class of problems). Debugging them ranges from impossible (if they&#8217;re suspected) to hard (if you have a stack trace of one actually happening).  At least in the newer JVMs the deadlock detector will actually point out the participants in a deadlock right there in the trace.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Landon</title>
		<link>http://www.hawksley.net/2009/02/the-hidden-danger-of-synchronization/comment-page-1/#comment-6</link>
		<dc:creator>Landon</dc:creator>
		<pubDate>Sat, 21 Feb 2009 13:09:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawksley.net/?p=48#comment-6</guid>
		<description>Very good and very true. I know about this stuff but its just amazing how often you forget it when coding and then have the dreaded task of debugging the application to see what&#039;s going wrong. Think about it early and it will save headaches later.

Synchronization is one of those things that when it works is absolutely amazing but, you have a greater chance of something going tits up when you are not experienced. Long live Erlang :)</description>
		<content:encoded><![CDATA[<p>Very good and very true. I know about this stuff but its just amazing how often you forget it when coding and then have the dreaded task of debugging the application to see what&#8217;s going wrong. Think about it early and it will save headaches later.</p>
<p>Synchronization is one of those things that when it works is absolutely amazing but, you have a greater chance of something going tits up when you are not experienced. Long live Erlang :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
