Hi,
I have an application which generates large zip files (SharpZipLib) on the fly. The content of the zip file is written directly to the unbuffered OutputStream, keeping the memory overhead on the server low.
It is not an option to create those zip files on disk and to send them with Response.TransmitFile.
I understand that the more zip files that are being created at the same time, the more CPU power is needed on the server.
The problem I have is that whenever I'm downloading a large file, I cannot use my browser to go to another page. The server responds only after having served the entire zip file. However, I'm still able to browse the site with an other browser or from an other client. It seems that IIS uses the same Thread to serve all request from the same browser, and since that thread is busy serving the zip file, all subsequent requests are queued.
I'm aware that creating a zip file on the fly uses u ...
Go to the complete details ...