On Mon, Jun 9, 2008 at 3:02 PM, Barney Boisvert <[EMAIL PROTECTED]> wrote:
> Use a content delivery network (CDN) or something like Amazon S3. > CDNs are usually targeted at large-scale anonymous access, which is > not quite what you want. S3, on the other hand, is private by > default, and can easily be accessed by secured URLs that are only > accessible for a narrow window of time. So someone requests your > asset, and instead of serving it with CFCONTENT, you redirect them to > S3 with a URL that's only good for a handful seconds. I do this for a > few different things, and it works like a charm. It also offloads the > bandwidth from my infrastructure to Amazon's. I could look, but what does S3's usage policy say about that kind of offloading? Does that also mean that the application now also has to maintain assets in 2 different places? Some of my users would really balk at that. But an intriguing suggestion, nonetheless. > You might be able to synthesize something like this with IIS, as well. > It won't server a given asset unless it has some one-time or > short-lived token attached to the URL. Set that up to protect your > downloads, and then do the same compute token/redirect thing to your > own IIS server and let it serve the file instead of CF. This seems more in line with keeping things in-house. I like that. Any pointers to where I could start? Or what I should google? :-) Thanks, George ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;192386516;25150098;k Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:307107 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
