<?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: A diagram</title>
	<atom:link href="http://blogs.linux.ie/balor/2006/09/15/a-diagram/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.linux.ie/balor/2006/09/15/a-diagram/</link>
	<description>We eat cats whilst you code.</description>
	<lastBuildDate>Thu, 17 May 2012 00:31:11 +0100</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.4</generator>
	<item>
		<title>By: Neal Chant</title>
		<link>http://blogs.linux.ie/balor/2006/09/15/a-diagram/comment-page-1/#comment-566</link>
		<dc:creator>Neal Chant</dc:creator>
		<pubDate>Tue, 19 Sep 2006 11:59:06 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.linux.ie/balor/?p=174#comment-566</guid>
		<description>I can see where you&#039;re going. The path to your nirvana is both rocky and muddy.

The flow doesn&#039;t seem right, you have Listen for Accept twice? With the 3 boxes aligned it *appears* that all 3 processes could be simultaneous, or, if that&#039;s not the case then there is no indication of how logic takes place.

Neal :)</description>
		<content:encoded><![CDATA[<p>I can see where you&#8217;re going. The path to your nirvana is both rocky and muddy.</p>
<p>The flow doesn&#8217;t seem right, you have Listen for Accept twice? With the 3 boxes aligned it *appears* that all 3 processes could be simultaneous, or, if that&#8217;s not the case then there is no indication of how logic takes place.</p>
<p>Neal <img src='http://blogs.linux.ie/balor/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: phil</title>
		<link>http://blogs.linux.ie/balor/2006/09/15/a-diagram/comment-page-1/#comment-560</link>
		<dc:creator>phil</dc:creator>
		<pubDate>Sun, 17 Sep 2006 11:45:38 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.linux.ie/balor/?p=174#comment-560</guid>
		<description>Hmm. 
A thread sends a message to the subnet, and then listens for accept. Now, the original thread is joined by two other, unrelated threads. It gets an accept, acknowledges it, and shuts down. Or else the 3 middle sections relate to the flow of events when an accept is received. But I still can&#039;t see what order they execute in.
Its possible that theres an explanation for all this, with context, but really I think you need to start from scratch.</description>
		<content:encoded><![CDATA[<p>Hmm.<br />
A thread sends a message to the subnet, and then listens for accept. Now, the original thread is joined by two other, unrelated threads. It gets an accept, acknowledges it, and shuts down. Or else the 3 middle sections relate to the flow of events when an accept is received. But I still can&#8217;t see what order they execute in.<br />
Its possible that theres an explanation for all this, with context, but really I think you need to start from scratch.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bart B</title>
		<link>http://blogs.linux.ie/balor/2006/09/15/a-diagram/comment-page-1/#comment-552</link>
		<dc:creator>Bart B</dc:creator>
		<pubDate>Fri, 15 Sep 2006 16:54:44 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.linux.ie/balor/?p=174#comment-552</guid>
		<description>I have to say I&#039;m stumped. Is this some for of state diagram, a sw=equence diagram, a networking diagram ... what? If it relates to software my advice would be to re-do it as some form of UML diagram. UML is standard so even if the kiddies don&#039;t get it the first time if they get this diagram explained to them they learn two things, what ever you are teaching them and some UML, which is a good thing for students to get familiar with!</description>
		<content:encoded><![CDATA[<p>I have to say I&#8217;m stumped. Is this some for of state diagram, a sw=equence diagram, a networking diagram &#8230; what? If it relates to software my advice would be to re-do it as some form of UML diagram. UML is standard so even if the kiddies don&#8217;t get it the first time if they get this diagram explained to them they learn two things, what ever you are teaching them and some UML, which is a good thing for students to get familiar with!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Des Traynor</title>
		<link>http://blogs.linux.ie/balor/2006/09/15/a-diagram/comment-page-1/#comment-550</link>
		<dc:creator>Des Traynor</dc:creator>
		<pubDate>Fri, 15 Sep 2006 11:35:49 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.linux.ie/balor/?p=174#comment-550</guid>
		<description>Can&#039;t help you here I&#039;m afraid. I can get as far as The dot (.) pings the subnet, and listens for accept. 

Then one of three things happen, or all three things happen in an order, or all three things can happen, but none of them are guaranteed. I have no idea whats happening there. 

Also, for the sake of a better diagram, if all three things end in shutdown, why move that outside, unless the shutdown method is different for each of the three cases, in which case you should clarify that. 

Bear in mind, people usually read top to bottom, left to right, so a diagrams typical flow should usually be that way. 

If one of three things is going to happen, have one box, with three outward arrows. If all three things must happen in order, have it as a chain of actions.</description>
		<content:encoded><![CDATA[<p>Can&#8217;t help you here I&#8217;m afraid. I can get as far as The dot (.) pings the subnet, and listens for accept. </p>
<p>Then one of three things happen, or all three things happen in an order, or all three things can happen, but none of them are guaranteed. I have no idea whats happening there. </p>
<p>Also, for the sake of a better diagram, if all three things end in shutdown, why move that outside, unless the shutdown method is different for each of the three cases, in which case you should clarify that. </p>
<p>Bear in mind, people usually read top to bottom, left to right, so a diagrams typical flow should usually be that way. </p>
<p>If one of three things is going to happen, have one box, with three outward arrows. If all three things must happen in order, have it as a chain of actions.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
