<?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: Preloading .flv and .mp3 files with Flash</title>
	<atom:link href="http://www.askapache.com/flash/preloading-caching-flv-mp3.html/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.askapache.com/flash/preloading-caching-flv-mp3.html</link>
	<description>Web Development</description>
	<pubDate>Sat, 17 May 2008 06:57:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Ken Luallen</title>
		<link>http://www.askapache.com/flash/preloading-caching-flv-mp3.html#comment-36131</link>
		<dc:creator>Ken Luallen</dc:creator>
		<pubDate>Sun, 17 Feb 2008 04:31:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com/flash/preloading-caching-flv-mp3.html#comment-36131</guid>
		<description>So you've covered flvs and mp3s... can you show us &lt;strong&gt;how to preload an xml's worth of jpgs / pngs&lt;/strong&gt;?  That would be magnificent!</description>
		<content:encoded><![CDATA[<p>So you&#8217;ve covered flvs and mp3s&#8230; can you show us <strong>how to preload an xml&#8217;s worth of jpgs / pngs</strong>?  That would be magnificent!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: janos erdelyi</title>
		<link>http://www.askapache.com/flash/preloading-caching-flv-mp3.html#comment-35648</link>
		<dc:creator>janos erdelyi</dc:creator>
		<pubDate>Fri, 01 Feb 2008 20:30:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com/flash/preloading-caching-flv-mp3.html#comment-35648</guid>
		<description>it would be a huge waste of bandwidth to *definitely* transfer many many bytes that will only *maybe* be accessed by a human if you were to scale this up to all sites taking this type of action.

however, for end-user experience it's great when clicking around.

what about a middle ground? download a certain sized byte-range as a buffer and then stream the rest out if they decide to watch/listen - that way they get an instant start, but fewer resources are used for things the end-user never clicked on.</description>
		<content:encoded><![CDATA[<p>it would be a huge waste of bandwidth to *definitely* transfer many many bytes that will only *maybe* be accessed by a human if you were to scale this up to all sites taking this type of action.</p>
<p>however, for end-user experience it&#8217;s great when clicking around.</p>
<p>what about a middle ground? download a certain sized byte-range as a buffer and then stream the rest out if they decide to watch/listen - that way they get an instant start, but fewer resources are used for things the end-user never clicked on.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- In 1.260 -->
