Sent from my iPhone On Jun 17, 2010, at 4:49 PM, Dave Watts <dwa...@figleaf.com> wrote:
> >> In other applications I routinely use cfcontent to serve protected >> files on >> extranet applications however the traffic ( 10-20 files/day) is >> nowhere near >> as rigorous as will be required here with 12,000 per day of 40Meg >> average >> per file. I am considering serving the files now through cfcontent >> via HTTP >> instead of FTP for a couple of reasons. 1) because most Internet >> Security >> programs block FTP and we have to help people (mostly kids) open >> the port >> and 2) to prevent direct linking to the files because this endeavor >> is >> funded by ads on the website (and my wallet). >> >> I know the most efficient way to serve this quantity and size of >> files is >> via ftp but what I don't know is what is required by the various CF >> engines >> AdobeCF, OpenBD, Bluedragon, Ralio to serve up the same via HTTP. >> Will our >> new server hardware handle that kind of HTTP file traffic (I >> suspect so), >> will OpenBD/Tomcat be up to the task or will I need a different >> CFML engine? >> Essentially what I need to know is what it would take to routinely >> serve >> that many/size files through the CF engine. I don't want to go down >> this >> road and find that people are having problems downloading because >> the CF >> engine / Web server can't keep up. Has anyone had experience with >> this and >> can you offer some advice? > > My advice for you would be to avoid using CFCONTENT for this, as it's > really not designed for this. Each request using CFCONTENT will use > one of your threads, I think, and there are decent alternatives. > > The alternative I'd recommend would be the use of temporary symlinks. > When someone is granted access to a file, you'd create a symlink for > that file, pointing to a web-accessible location, then let the user > download it via HTTP. Sometime after, you'd delete the symlink. > Exactly how long after, I'm not sure - that would be a balance of > convenience to the user (in case they don't download it immediately) > versus the potential for abuse (the user provides the link to someone > else). > > Dave Watts, CTO, Fig Leaf Software > http://www.figleaf.com/ > http://training.figleaf.com/ > > Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on > GSA Schedule, and provides the highest caliber vendor-authorized > instruction at our training centers, online, or onsi > I would highly recommend using a Content Delivery Network like Mosso Files to store your files, then you can symlink to them by passing headers as a re-direct. This way you don't have the overhead of distribution, hardware and requests... You pay a small fee per month for transfer and storage. Do a cost analysis, including your time and sys admin time in upgrades to handle all of this badwidth. Check out the CDN writeup on openboxitsolutions.com for some real life examples and price savings.. Feel free to reach out to me, as well for more information. I highly recommend not hosting static delivery especially to the extent you're looking at without weighing CDN options. William Attwood Systems Engineer Software Engineer 801-859-2987 > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:334634 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
