What about in digital asset distribution, such as ESD's?

Does CFCONTENT store the file in memory before it serves it to the client?
If so, then won't your server crash (or will the user just experience a long
wait before the data is sent) if you have 15 clients downloading an 80 MB
file at one time?  Or does CFCONTENT stream the file data?

Thoughts?

-- 
SCOTT VAN VLIET 
SENIOR ANALYST 
SBC SERVICES, INC 
Tel: 858.886.3878 
Fax: 858.653.6763 
Email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 




-----Original Message-----
From: Chambers, Bryan (NE) [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 21, 2002 12:55 PM
To: CF-Talk
Subject: RE: Password Protected File Downloads


Hi Jim,

CFCONTENT may be the way to go to serve up the files.  The files to be
downloaded would sit outside of the webroot so it would be impossible to get
to them by typing in a URL.

-Bryan

-----Original Message-----
From: Jim Curran [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 21, 2002 2:54 PM
To: CF-Talk
Subject: Password Protected File Downloads


Hey all,

What is the most efficient way to provide files for download to a client
after username/password authentication *without* using NT Authentication.

The simple way is to validate the user using CF and then just display the
documents using CFDirectory, but, if anyone know the URL to the document,
they can bypass the cfm template altogether.  I was thinking about randomly
renaming documents and storing the filenames in a DB, but that seems sloppy
too.

This client is currently in a virtual hosting environment, so adding
directory security seems out of the question.

Any thoughts would be greatly appreciated.

TIA,

- jim




______________________________________________________________________
Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to