<?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: jeff barr amazon web services presentation</title>
	<atom:link href="http://blog.moopsfc.com/37/2006/05/15/jeff-barr-amazon-web-services-presentation/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.moopsfc.com/37/2006/05/15/jeff-barr-amazon-web-services-presentation/</link>
	<description>the continuing saga of your hero</description>
	<lastBuildDate>Sun, 14 Mar 2010 18:00:59 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: brodie bruce</title>
		<link>http://blog.moopsfc.com/37/2006/05/15/jeff-barr-amazon-web-services-presentation/comment-page-1/#comment-208</link>
		<dc:creator>brodie bruce</dc:creator>
		<pubDate>Tue, 16 May 2006 15:05:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.moopsfc.com/37/2006/05/15/jeff-barr-amazon-web-services-presentation/#comment-208</guid>
		<description>webdav is similar, but adds a lot of unnecessary features for the target usage. the spec is too complicated and also requires xml. xml jammed into headers no less. the one feature from webdav that may be useful is a way to get a directory listing in a data format. however, i suspect the target usage is a scenario where the files stored are known by the client application that directly use the urls. it may be possible to do directory listings. i didn&#039;t really look at the docs that much.</description>
		<content:encoded><![CDATA[<p>webdav is similar, but adds a lot of unnecessary features for the target usage. the spec is too complicated and also requires xml. xml jammed into headers no less. the one feature from webdav that may be useful is a way to get a directory listing in a data format. however, i suspect the target usage is a scenario where the files stored are known by the client application that directly use the urls. it may be possible to do directory listings. i didn&#8217;t really look at the docs that much.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gregg</title>
		<link>http://blog.moopsfc.com/37/2006/05/15/jeff-barr-amazon-web-services-presentation/comment-page-1/#comment-207</link>
		<dc:creator>gregg</dc:creator>
		<pubDate>Tue, 16 May 2006 13:59:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.moopsfc.com/37/2006/05/15/jeff-barr-amazon-web-services-presentation/#comment-207</guid>
		<description>I would think that webDAV, for which implementations are available, could met this need. I believe there is also a specification. I used clients that work well, like any file explorer GUI. Of course, the same issue with all solutions is that different implementations can&#039;t seem to meet the specifications the same way. What do you think it takes to get accurate implementations?</description>
		<content:encoded><![CDATA[<p>I would think that webDAV, for which implementations are available, could met this need. I believe there is also a specification. I used clients that work well, like any file explorer GUI. Of course, the same issue with all solutions is that different implementations can&#8217;t seem to meet the specifications the same way. What do you think it takes to get accurate implementations?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
