<?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:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: Beta Release: DotNetNuke Amazon S3 Folder Integration Providers</title>
	<atom:link href="http://blogs.law.harvard.edu/brandonhaynes/2009/06/22/released-dotnetnuke-amazon-s3-folder-integration-providers/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.law.harvard.edu/brandonhaynes/2009/06/22/released-dotnetnuke-amazon-s3-folder-integration-providers/</link>
	<description>Observations about the intersection of technology, business, and intellectual property</description>
	<lastBuildDate>Wed, 21 Oct 2009 16:16:51 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Brandon Haynes</title>
		<link>http://blogs.law.harvard.edu/brandonhaynes/2009/06/22/released-dotnetnuke-amazon-s3-folder-integration-providers/comment-page-1/#comment-2511</link>
		<dc:creator>Brandon Haynes</dc:creator>
		<pubDate>Wed, 23 Sep 2009 12:09:10 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/brandonhaynes/?p=199#comment-2511</guid>
		<description>Hi Adam,

The S3 provider utilizes the authorization architecture introduced in DotNetNuke 5.1.  As such, it is not available for extension in the 4.x line and S3 integration is therefore not possible in this version without (significant) core modification.  It is likely that an upgrade to 5.x (in particular, 5.1.2 is a highly stable choice) will be your sole recourse for S3 functionality.

B</description>
		<content:encoded><![CDATA[<p>Hi Adam,</p>
<p>The S3 provider utilizes the authorization architecture introduced in DotNetNuke 5.1.  As such, it is not available for extension in the 4.x line and S3 integration is therefore not possible in this version without (significant) core modification.  It is likely that an upgrade to 5.x (in particular, 5.1.2 is a highly stable choice) will be your sole recourse for S3 functionality.</p>
<p>B</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Jones</title>
		<link>http://blogs.law.harvard.edu/brandonhaynes/2009/06/22/released-dotnetnuke-amazon-s3-folder-integration-providers/comment-page-1/#comment-2510</link>
		<dc:creator>Adam Jones</dc:creator>
		<pubDate>Wed, 23 Sep 2009 06:11:45 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/brandonhaynes/?p=199#comment-2510</guid>
		<description>I have over 8,000 photos listed: 

http://yokosukabase.com/pics.aspx 

I think I need S3 amazon integration.. It would help with performance, and for storage space. Thanks!

I am running 4.9.5 and dont plan to migrate to 5 for a few more months.  If there is a way, that you can make this API available on the 4 release, that would be fantastic.  I wouldnt mind testing this capability, and seeing if I can get things working..</description>
		<content:encoded><![CDATA[<p>I have over 8,000 photos listed: </p>
<p><a href="http://yokosukabase.com/pics.aspx" rel="nofollow">http://yokosukabase.com/pics.aspx</a> </p>
<p>I think I need S3 amazon integration.. It would help with performance, and for storage space. Thanks!</p>
<p>I am running 4.9.5 and dont plan to migrate to 5 for a few more months.  If there is a way, that you can make this API available on the 4 release, that would be fantastic.  I wouldnt mind testing this capability, and seeing if I can get things working..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon Haynes</title>
		<link>http://blogs.law.harvard.edu/brandonhaynes/2009/06/22/released-dotnetnuke-amazon-s3-folder-integration-providers/comment-page-1/#comment-2506</link>
		<dc:creator>Brandon Haynes</dc:creator>
		<pubDate>Fri, 11 Sep 2009 12:15:29 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/brandonhaynes/?p=199#comment-2506</guid>
		<description>@Karl I&#039;ll look at attempting to reproduce your issue.  In the meantime, I suggest using a debugging proxy (such as Fiddler) to see where the link handler is attempting to redirect to; that will yield insight as to whether the problem is with the provider or is an S3 configuration issue.

If you could open a work item on the project website outlining this issue, it would be greatly appreciated.

B</description>
		<content:encoded><![CDATA[<p>@Karl I&#8217;ll look at attempting to reproduce your issue.  In the meantime, I suggest using a debugging proxy (such as Fiddler) to see where the link handler is attempting to redirect to; that will yield insight as to whether the problem is with the provider or is an S3 configuration issue.</p>
<p>If you could open a work item on the project website outlining this issue, it would be greatly appreciated.</p>
<p>B</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl</title>
		<link>http://blogs.law.harvard.edu/brandonhaynes/2009/06/22/released-dotnetnuke-amazon-s3-folder-integration-providers/comment-page-1/#comment-2501</link>
		<dc:creator>Karl</dc:creator>
		<pubDate>Tue, 01 Sep 2009 02:49:51 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/brandonhaynes/?p=199#comment-2501</guid>
		<description>Everything works except for clicking on the link in a HTML/Text box. When configuring a link on an HTML/Text box, I can see the directories and select a file. When I click on the link, the web page cannot be opened. Using Cloudberry Explorer, I&#039;ve tried to give every ACL group and user read permission and I even created a user call everyone and I gave it read permission.


Any ideas?</description>
		<content:encoded><![CDATA[<p>Everything works except for clicking on the link in a HTML/Text box. When configuring a link on an HTML/Text box, I can see the directories and select a file. When I click on the link, the web page cannot be opened. Using Cloudberry Explorer, I&#8217;ve tried to give every ACL group and user read permission and I even created a user call everyone and I gave it read permission.</p>
<p>Any ideas?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon Haynes</title>
		<link>http://blogs.law.harvard.edu/brandonhaynes/2009/06/22/released-dotnetnuke-amazon-s3-folder-integration-providers/comment-page-1/#comment-2458</link>
		<dc:creator>Brandon Haynes</dc:creator>
		<pubDate>Tue, 11 Aug 2009 19:40:25 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/brandonhaynes/?p=199#comment-2458</guid>
		<description>@Jonathan: The DotNetNuke providers are one of the (many) valid methods by which one may safely extend the framework; this extension is, therefore, appropriate (and does not modify the core in any way).  One could, however, make a reasonable argument that the data provider is the &quot;least safe&quot; such provider.  C&#039;est la vie.

With respect file corruption, I have seen circumstances where AmazonS3 will report an error directly in the file stream (and the resultant attempt to interpret the data as, say, a JPEG will appear as corruption).  Try persisting the file to disk and examining it with a text editor.  Sometimes the permission problem will become evident in the text.

@Tozzi: The extension is complied against the 5.1 version, but does (to my recollection) not utilize any functionality that is not available in the 4.x line.  A recompilation against 4.9.4 should be fairly straightforward, though there will be some small API changes that are necessary due to method obsolescence.  

B</description>
		<content:encoded><![CDATA[<p>@Jonathan: The DotNetNuke providers are one of the (many) valid methods by which one may safely extend the framework; this extension is, therefore, appropriate (and does not modify the core in any way).  One could, however, make a reasonable argument that the data provider is the &#8220;least safe&#8221; such provider.  C&#8217;est la vie.</p>
<p>With respect file corruption, I have seen circumstances where AmazonS3 will report an error directly in the file stream (and the resultant attempt to interpret the data as, say, a JPEG will appear as corruption).  Try persisting the file to disk and examining it with a text editor.  Sometimes the permission problem will become evident in the text.</p>
<p>@Tozzi: The extension is complied against the 5.1 version, but does (to my recollection) not utilize any functionality that is not available in the 4.x line.  A recompilation against 4.9.4 should be fairly straightforward, though there will be some small API changes that are necessary due to method obsolescence.  </p>
<p>B</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tozzi</title>
		<link>http://blogs.law.harvard.edu/brandonhaynes/2009/06/22/released-dotnetnuke-amazon-s3-folder-integration-providers/comment-page-1/#comment-2457</link>
		<dc:creator>Tozzi</dc:creator>
		<pubDate>Tue, 11 Aug 2009 19:04:34 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/brandonhaynes/?p=199#comment-2457</guid>
		<description>Excellent extension, a great idea to leverage the cloud storage especially for high volume sites. My ISP hosts a DNN site that pushes in excess of 80 GIGs a month and storing this in the cloud will be awesome!

One grip, the extension requires DNN 5.1+ and we&#039;re running over 100 sites on DNN 4.x.x which will not be upgraded any time soon. How much effort to make this backward compatible with the 4.x branch?</description>
		<content:encoded><![CDATA[<p>Excellent extension, a great idea to leverage the cloud storage especially for high volume sites. My ISP hosts a DNN site that pushes in excess of 80 GIGs a month and storing this in the cloud will be awesome!</p>
<p>One grip, the extension requires DNN 5.1+ and we&#8217;re running over 100 sites on DNN 4.x.x which will not be upgraded any time soon. How much effort to make this backward compatible with the 4.x branch?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan</title>
		<link>http://blogs.law.harvard.edu/brandonhaynes/2009/06/22/released-dotnetnuke-amazon-s3-folder-integration-providers/comment-page-1/#comment-2408</link>
		<dc:creator>Jonathan</dc:creator>
		<pubDate>Mon, 03 Aug 2009 21:33:34 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/brandonhaynes/?p=199#comment-2408</guid>
		<description>The files are corrupt when I try to open them from either DNN File Manager or the Links module. They were uploaded with CloudBerry.

Any ideas?

Thanks!</description>
		<content:encoded><![CDATA[<p>The files are corrupt when I try to open them from either DNN File Manager or the Links module. They were uploaded with CloudBerry.</p>
<p>Any ideas?</p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan</title>
		<link>http://blogs.law.harvard.edu/brandonhaynes/2009/06/22/released-dotnetnuke-amazon-s3-folder-integration-providers/comment-page-1/#comment-2406</link>
		<dc:creator>Jonathan</dc:creator>
		<pubDate>Mon, 03 Aug 2009 18:03:21 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/brandonhaynes/?p=199#comment-2406</guid>
		<description>Hi Brandon -- Thanks for creating this. I&#039;m playing around with it and it appears to work well.

Can you clarify whether or not changing the data provider to your provider conflicts with your goal of not changing the &quot;core&quot;? 

Thanks.</description>
		<content:encoded><![CDATA[<p>Hi Brandon &#8212; Thanks for creating this. I&#8217;m playing around with it and it appears to work well.</p>
<p>Can you clarify whether or not changing the data provider to your provider conflicts with your goal of not changing the &#8220;core&#8221;? </p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex Shirley</title>
		<link>http://blogs.law.harvard.edu/brandonhaynes/2009/06/22/released-dotnetnuke-amazon-s3-folder-integration-providers/comment-page-1/#comment-2324</link>
		<dc:creator>Alex Shirley</dc:creator>
		<pubDate>Sat, 25 Jul 2009 20:33:04 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/brandonhaynes/?p=199#comment-2324</guid>
		<description>&gt; Alex Shirley will certainly yell at me for doing this
Yell! Yell! Yell!
- of course you were right :).</description>
		<content:encoded><![CDATA[<p>&gt; Alex Shirley will certainly yell at me for doing this<br />
Yell! Yell! Yell!<br />
- of course you were right <img src='http://blogs.law.harvard.edu/brandonhaynes/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: From the Desk of Brandon Haynes &#187; Presentation Materials: Advanced Authorization in DotNetNuke 5.1</title>
		<link>http://blogs.law.harvard.edu/brandonhaynes/2009/06/22/released-dotnetnuke-amazon-s3-folder-integration-providers/comment-page-1/#comment-1735</link>
		<dc:creator>From the Desk of Brandon Haynes &#187; Presentation Materials: Advanced Authorization in DotNetNuke 5.1</dc:creator>
		<pubDate>Mon, 22 Jun 2009 19:17:47 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/brandonhaynes/?p=199#comment-1735</guid>
		<description>[...] are displayed right).  The code for this demonstration will be made available later this month on its project homepage at [...]</description>
		<content:encoded><![CDATA[<p>[...] are displayed right).  The code for this demonstration will be made available later this month on its project homepage at [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
