>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?
>

I've gotta disagree with you there. It's not going away, and files will get larger as average connection speeds improve, audio blogging apps proliferate, etc. Also looking at Web Forms 2.0, the support for file uploading options is growing. I'm looking for WWWC apps to be self-contained, and this is an important piece for us.

>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.
>

I'll post something further on your site, as I see you're starting to look toward the needs for the next version.

-- Randy