title: Does parallel work in an ASP.NET work process block connection threads?
body: <p>i'm not sure I've used the correct terms in the title but this is my question.</p>
  
  <p>If i have a stock standard ASP.NET webpage (webforms or mvc) and i wish to do some longish processing, I create a new process and fire that off. </p>
  
  <p>Eg. save an uploaded file to a local folder then do some image manipulation on it
  Eg. save an uploaded video to a local folder then do some video encoding on it.</p>
  
  <p>So while this process is doing it's thing, will it effectively block on available connection hitting the IIS server, to be processed/handled?</p>
  
  <p>Like, I heard there was a finite number of connections that can get processed at once ... which is the number of threads on the ... err thread-queue? Hmm. </p>
  
  <p>Basically, can i have some background tasks going ahead and it doesn't impact the number of possible requests i can process.</p>