<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wikidot="http://www.wikidot.com/rss-namespace">

	<channel>
		<title>Comments for page &quot;Distributed Computing: The Survey Pattern&quot;</title>
		<link>http://250bpm.com/blog:5/comments/show</link>
		<description></description>
				<copyright></copyright>
		<lastBuildDate>Sat, 01 Aug 2015 21:42:26 +0000</lastBuildDate>
		
					<item>
				<guid>http://250bpm.com/blog:5/comments/show#post-1836720</guid>
				<title>(no title)</title>
				<link>http://250bpm.com/blog:5/comments/show#post-1836720</link>
				<description></description>
				<pubDate>Tue, 20 Aug 2013 16:30:36 +0000</pubDate>
				<wikidot:authorName>Will</wikidot:authorName>								<content:encoded>
					<![CDATA[
						 <p>Ok, so if I don't know the locations of my peers, I'll need to discover through some other mechanism. But after that, I get a nice pattern for consensus, for example.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://250bpm.com/blog:5/comments/show#post-1836598</guid>
				<title>(no title)</title>
				<link>http://250bpm.com/blog:5/comments/show#post-1836598</link>
				<description></description>
				<pubDate>Tue, 20 Aug 2013 13:12:49 +0000</pubDate>
				<wikidot:authorName>Martin Sustrik</wikidot:authorName>								<content:encoded>
					<![CDATA[
						 <p>You establish the topology explicitely.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://250bpm.com/blog:5/comments/show#post-1836596</guid>
				<title>(no title)</title>
				<link>http://250bpm.com/blog:5/comments/show#post-1836596</link>
				<description></description>
				<pubDate>Tue, 20 Aug 2013 13:10:13 +0000</pubDate>
				<wikidot:authorName>Will</wikidot:authorName>								<content:encoded>
					<![CDATA[
						 <p>What's the underlying protocol used in discovery?</p> <p>Multicast?</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://250bpm.com/blog:5/comments/show#post-1471107</guid>
				<title>(no title)</title>
				<link>http://250bpm.com/blog:5/comments/show#post-1471107</link>
				<description></description>
				<pubDate>Tue, 05 Jun 2012 08:05:43 +0000</pubDate>
				<wikidot:authorName>martin_sustrik</wikidot:authorName>				<wikidot:authorUserId>939</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Oops! Thanks for spotting it. It's fixed now.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://250bpm.com/blog:5/comments/show#post-1470919</guid>
				<title>(no title)</title>
				<link>http://250bpm.com/blog:5/comments/show#post-1470919</link>
				<description></description>
				<pubDate>Tue, 05 Jun 2012 03:43:03 +0000</pubDate>
				<wikidot:authorName>Christopher Smith</wikidot:authorName>								<content:encoded>
					<![CDATA[
						 <p>I think you accidentally flipped your word choice here:</p> <blockquote> <p>Second, timeout for the survey is set to 1000 milliseconds (1 second). This is more than sufficient on a local area network, where latencies are measured in microseconds. However, on wide area network, especially if <strong>low latency (satellite or similar) links</strong> are involved you may wish to make the timeout longer.</p> </blockquote> <p>I'm all but certain you mean it to read:</p> <blockquote> <p>Second, timeout for the survey is set to 1000 milliseconds (1 second). This is more than sufficient on a local area network, where latencies are measured in microseconds. However, on wide area network, especially if <em>high latency (satellite or similar) links</em> are involved you may wish to make the timeout longer.</p> </blockquote> 
				 	]]>
				</content:encoded>							</item>
				</channel>
</rss>