File buffering with CFCONTENT

[perlyking]

Does anyone know how exactly <cfcontent> works when 'streaming' files back to
the client?

I have an application that uses <cfcontent> to deliver files securely from an
area on the server file system outside the document root.

e.g.
<cfif permissions and security checks are ok...>
<cfheader blah ...>
<cfcontent type="application/unknown" file="/path/to/large/file"
deletefile="no">

Is the file read into RAM as a whole before the download begins, or are
sequential chunks read from disk, buffered, and passed to the client?

This is an important issue for me because I need to stream large files
(200mb+) and I don't want multiple concurrent downloads to kill the server.

[Pete Thomas]

Not absolutely sure about cfcontent but I would guess it is the similar
mechanism to that of cffile where the data is a java inputstream and is not
buffered into RAM I guess a good way to find out would be to deliver a very
large file and look at your memory usage. I suspect it will be good