<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:gml="http://www.opengis.net/gml"
	>
<channel>
	<title>Comments on: 40</title>
	<atom:link href="http://xyzzyxyzzy.net/2009/07/11/40/feed/" rel="self" type="application/rss+xml" />
	<link>http://xyzzyxyzzy.net/2009/07/11/40/</link>
	<description>...you are in a grid of twisty, little links, all alike. there's a teleport gate here.</description>
	<lastBuildDate>Fri, 16 Dec 2011 14:43:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Darryl</title>
		<link>http://xyzzyxyzzy.net/2009/07/11/40/comment-page-1/#comment-307</link>
		<dc:creator>Darryl</dc:creator>
		<pubDate>Wed, 15 Jul 2009 01:37:13 +0000</pubDate>
		<guid isPermaLink="false">http://xyzzyxyzzy.net/?p=343#comment-307</guid>
		<description>&lt;p&gt;Great news!  Interesting that breaking out the texture traffic to a separate thread made such a difference...&lt;/p&gt;

&lt;p&gt;I have thought for some time that texture loading causes a lot of clogging for the hosting server who is plagued with an influx of avis who request all the textures within sight.&lt;/p&gt;

&lt;p&gt;But since textures on a grid come from a common asset server, what if ANY server in the grid could cache and serve texture requests from any region in the grid?  We could avoid clogging any single network interface, and distribute load to grid servers which are idle or least busy... and the asymmetric nature of most broadband connections would allow for a massive bandwidth spike (much like bittorrent) to satisfy the client&#039;s texture requests relatively quickly, even as the server the client is in is busy dealing with things like physics and communications.&lt;/p&gt;

&lt;p&gt;Just a thought... :)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Great news!  Interesting that breaking out the texture traffic to a separate thread made such a difference&#8230;</p>

<p>I have thought for some time that texture loading causes a lot of clogging for the hosting server who is plagued with an influx of avis who request all the textures within sight.</p>

<p>But since textures on a grid come from a common asset server, what if ANY server in the grid could cache and serve texture requests from any region in the grid?  We could avoid clogging any single network interface, and distribute load to grid servers which are idle or least busy&#8230; and the asymmetric nature of most broadband connections would allow for a massive bandwidth spike (much like bittorrent) to satisfy the client&#8217;s texture requests relatively quickly, even as the server the client is in is busy dealing with things like physics and communications.</p>

<p>Just a thought&#8230; <img src='http://xyzzyxyzzy.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>]]></content:encoded>
	</item>
</channel>
</rss>

