<?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: One Ring to Rule them all</title>
	<atom:link href="http://blogidol.ca/2010/05/one-ring-to-rule-the-all/875/feed" rel="self" type="application/rss+xml" />
	<link>http://blogidol.ca/2010/05/one-ring-to-rule-the-all/875</link>
	<description>The most powerful voices in Canadian IT.</description>
	<lastBuildDate>Mon, 06 Feb 2012 09:56:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Ron Van Holst</title>
		<link>http://blogidol.ca/2010/05/one-ring-to-rule-the-all/875/comment-page-1#comment-873</link>
		<dc:creator>Ron Van Holst</dc:creator>
		<pubDate>Wed, 05 May 2010 13:24:03 +0000</pubDate>
		<guid isPermaLink="false">http://blogidol.ca/?p=875#comment-873</guid>
		<description>That&#039;s a good point Chris.  These are &#039;wirespeed&#039; bit rates, the number of bits per second at the physical interface, it doesn&#039;t matter whether its copper, optical or radio.  The actual payload &#039;throughput&#039; is quite a bit less; it depends on the number and types of protocol layers between the physical layer and the application layer which each add their own overheads eating into the performance; and on the quality of the channel; noise in the channel for instance could trigger a lot of retransmissions if you&#039;re using TCP which will really hammer your throughput. Noise increases with distance for all media.  Shared medium like radio will also spend some of their bandwidth on negotiating time slots for participants; you probably have more that a few devices in your wireless N network.</description>
		<content:encoded><![CDATA[<p>That&#8217;s a good point Chris.  These are &#8216;wirespeed&#8217; bit rates, the number of bits per second at the physical interface, it doesn&#8217;t matter whether its copper, optical or radio.  The actual payload &#8216;throughput&#8217; is quite a bit less; it depends on the number and types of protocol layers between the physical layer and the application layer which each add their own overheads eating into the performance; and on the quality of the channel; noise in the channel for instance could trigger a lot of retransmissions if you&#8217;re using TCP which will really hammer your throughput. Noise increases with distance for all media.  Shared medium like radio will also spend some of their bandwidth on negotiating time slots for participants; you probably have more that a few devices in your wireless N network.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Lau</title>
		<link>http://blogidol.ca/2010/05/one-ring-to-rule-the-all/875/comment-page-1#comment-869</link>
		<dc:creator>Chris Lau</dc:creator>
		<pubDate>Wed, 05 May 2010 12:11:20 +0000</pubDate>
		<guid isPermaLink="false">http://blogidol.ca/?p=875#comment-869</guid>
		<description>While I cannot really comment on 40G (I don&#039;t know enough about this area of IT), I still find it hard to believe that wireless N connections for the home network at 300Mbps is faster than the wired one at 100Mbps (theoretically, and dependent on distance from router).</description>
		<content:encoded><![CDATA[<p>While I cannot really comment on 40G (I don&#8217;t know enough about this area of IT), I still find it hard to believe that wireless N connections for the home network at 300Mbps is faster than the wired one at 100Mbps (theoretically, and dependent on distance from router).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

