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