<?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"
	>
<channel>
	<title>Comments on: BitTorrent basics - protocol etc</title>
	<atom:link href="http://niallohiggins.com/2007/07/10/bittorrent-basics-protocol-etc/feed/" rel="self" type="application/rss+xml" />
	<link>http://niallohiggins.com/2007/07/10/bittorrent-basics-protocol-etc/</link>
	<description>The website of Niall O'Higgins: A few, immature words</description>
	<pubDate>Thu, 20 Nov 2008 20:03:30 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: BitTorrent Strategies: The Beginning &#124; Niall's Weblog</title>
		<link>http://niallohiggins.com/2007/07/10/bittorrent-basics-protocol-etc/#comment-41</link>
		<dc:creator>BitTorrent Strategies: The Beginning &#124; Niall's Weblog</dc:creator>
		<pubDate>Fri, 28 Dec 2007 15:33:00 +0000</pubDate>
		<guid isPermaLink="false">http://niallohiggins.com/2007/07/10/bittorrent-basics-protocol-etc/#comment-41</guid>
		<description>[...] existing data, in other words, from scratch. As I described in one of my earlier articles about the basics of the BitTorrent protocol, torrents are divided into units called pieces. The torrent meta data contains the SHA-1 checksums [...]</description>
		<content:encoded><![CDATA[<p>[...] existing data, in other words, from scratch. As I described in one of my earlier articles about the basics of the BitTorrent protocol, torrents are divided into units called pieces. The torrent meta data contains the SHA-1 checksums [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BitTorrent Distributed Hash Table (DHT) or Trackerless BitTorrent &#124; Niall's Weblog</title>
		<link>http://niallohiggins.com/2007/07/10/bittorrent-basics-protocol-etc/#comment-35</link>
		<dc:creator>BitTorrent Distributed Hash Table (DHT) or Trackerless BitTorrent &#124; Niall's Weblog</dc:creator>
		<pubDate>Tue, 25 Dec 2007 02:12:12 +0000</pubDate>
		<guid isPermaLink="false">http://niallohiggins.com/2007/07/10/bittorrent-basics-protocol-etc/#comment-35</guid>
		<description>[...] introduction of a distributed hash table implementation. As mentioned in my previous article on the basics of the BitTorrent protocol, traditionally BitTorrent relies upon a centralised &#8220;tracker&#8221; application - which runs [...]</description>
		<content:encoded><![CDATA[<p>[...] introduction of a distributed hash table implementation. As mentioned in my previous article on the basics of the BitTorrent protocol, traditionally BitTorrent relies upon a centralised &#8220;tracker&#8221; application - which runs [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Niall&#8217;s Weblog &#187; Blog Archive &#187; BitTorrent encryption, MSE basics</title>
		<link>http://niallohiggins.com/2007/07/10/bittorrent-basics-protocol-etc/#comment-12</link>
		<dc:creator>Niall&#8217;s Weblog &#187; Blog Archive &#187; BitTorrent encryption, MSE basics</dc:creator>
		<pubDate>Sun, 29 Jul 2007 20:35:36 +0000</pubDate>
		<guid isPermaLink="false">http://niallohiggins.com/2007/07/10/bittorrent-basics-protocol-etc/#comment-12</guid>
		<description>[...] I have been working quite a bit recently on my BitTorrent implementation. My project is faring reasonably well so far - it can successfully download large real-world torrents at decent speed. In the course of development, so far I have been focusing solely on the core specification, as documented here. Having gotten support for peer connections - outgoing and incoming - working, I started to notice something. Some peers would send ostensibly random data to my client. Investigation of this led me to conclude these were peers using the Message Stream Encryption protocol. [...]</description>
		<content:encoded><![CDATA[<p>[...] I have been working quite a bit recently on my BitTorrent implementation. My project is faring reasonably well so far - it can successfully download large real-world torrents at decent speed. In the course of development, so far I have been focusing solely on the core specification, as documented here. Having gotten support for peer connections - outgoing and incoming - working, I started to notice something. Some peers would send ostensibly random data to my client. Investigation of this led me to conclude these were peers using the Message Stream Encryption protocol. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rakshasa</title>
		<link>http://niallohiggins.com/2007/07/10/bittorrent-basics-protocol-etc/#comment-10</link>
		<dc:creator>Rakshasa</dc:creator>
		<pubDate>Thu, 19 Jul 2007 22:52:00 +0000</pubDate>
		<guid isPermaLink="false">http://niallohiggins.com/2007/07/10/bittorrent-basics-protocol-etc/#comment-10</guid>
		<description>RTorrent isn't huge, it's just big-boned.</description>
		<content:encoded><![CDATA[<p>RTorrent isn&#8217;t huge, it&#8217;s just big-boned.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: z004482js449sdgnq129</title>
		<link>http://niallohiggins.com/2007/07/10/bittorrent-basics-protocol-etc/#comment-7</link>
		<dc:creator>z004482js449sdgnq129</dc:creator>
		<pubDate>Mon, 16 Jul 2007 17:02:47 +0000</pubDate>
		<guid isPermaLink="false">http://niallohiggins.com/2007/07/10/bittorrent-basics-protocol-etc/#comment-7</guid>
		<description>please, publish the code :) this sounds excellent [i'm currently using rtorrent]</description>
		<content:encoded><![CDATA[<p>please, publish the code <img src='http://niallohiggins.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> this sounds excellent [i'm currently using rtorrent]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
