With integrated pipeline, all requests are passed through ASP.NET, including images, CSS.
Whereas, in classic pipeline, only requests for ASPX pages are by default passed through ASP.NET.
Could integrated pipeline negatively affect thread usage?
Suppose I request 500 MB binary file from an IIS server:
- With integrated pipeline, an ASP.NET worker thread would be used for the binary download (right?).
- With classic pipeline, the request is served directly by IIS, so no ASP.NET thread is used.
To me, this favors classic pipeline, as I would like as many threads as possible to serve ASPX pages.
Am I completely off base here?