>>Maybe we could have a special output option that would allow streaming output to a file and having wc.dll automatically pick up this file for reading its output. Gotta give this some thought. Something like you'd return the following string:
>>
>>WcResponseFile: d:\temp\somefile.pdf
>>
>>and the DLL would then read and delete this file after it's done streaming.
>
>Something like this would be interesting, yes. I wouldn't want the *deletion* to be automatic, though, because it might be best just to point to a true physical location where the permanent file is stored. Say you wanted a pay-per-download library where the WWWC app was adjudicating whether or not a user could download a file. Once you decide yes, just point WC.DLL to the library file location. (Part of the use case here is avoiding the security issue where there's a true HTTP path to the physical files available to someone who can guess the URL. Thus the need to point the DLL to files in a physical location.)
>
>In general, handling of large files is now the single biggest challenge we have with respect to working within the WWWC/VFP framework. The other half is the upload side. Right now if a file is bigger than 16MB, you can't use WWWC, because wwRequest.getMultipartFile() requires that you can load the full file contents into a VFP string variable. For seasoned users, FTP is a possibility, but that's a real pain, forcing you to set up a whole separate process, maintain the folders, cope with security issues, etc.
>
>So, if you contemplate a technique for dishing out large files, it would be great if a complementary way of extracting them from HTTP uploads could be added. This might be doable under file-based currently via some direct LLFF on the temp file, but for COM, again the solution would need to occur back with the ISAPI DLL.
>
>Thanks for considering these needs.
>
>-- Randy

I need to give this some thought... The input end is going to be problematic unless the input includes some special parameter to let WWWC know to not dump the output into a string.

FWIW, uploading files this large should be outlawed <g>... the browser UI to do this will make most people give up no?

Sending is a more likely scenario. We can add something like Response.TransmitFile() that IIS has and that would set a special flag in the output to tell wc.dll to send output directly from a file.

+++ Rick ---