<?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: How Skype network handles scalability..</title>
	<atom:link href="http://www.royans.net/arch/how-skype-network-handles-scalability/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.royans.net/arch/how-skype-network-handles-scalability/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=how-skype-network-handles-scalability</link>
	<description>Building reliable, high performance, highly available clusters</description>
	<lastBuildDate>Sun, 07 Mar 2010 16:57:09 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<atom:link rel="hub" href="http://pubsubhubbub.appspot.com" />
	<atom:link rel="hub" href="http://superfeedr.com/hubbub" />
		<item>
		<title>By: Scalable web architectures &#187; Blog Archive &#187; P2P network scalability</title>
		<link>http://www.royans.net/arch/how-skype-network-handles-scalability/comment-page-1/#comment-38</link>
		<dc:creator>Scalable web architectures &#187; Blog Archive &#187; P2P network scalability</dc:creator>
		<pubDate>Tue, 11 Sep 2007 07:50:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.royans.net/arch/2007/08/20/how-skype-network-handles-scalability/#comment-38</guid>
		<description>[...] died after RIAA revolt. Skype, as it happens, also has its roots in P2P network [ Skype protocol , Skype scalability problems ] and has been doing pretty good over the years. So its no surprise that Joost chose P2P model [...]</description>
		<content:encoded><![CDATA[<p>[...] died after RIAA revolt. Skype, as it happens, also has its roots in P2P network [ Skype protocol , Skype scalability problems ] and has been doing pretty good over the years. So its no surprise that Joost chose P2P model [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
