title: Web API Service - How to make the requests at the server to be executed concurrently
body: <p>I am using a WebApi rest service controller, hosted by IIS 7.5,
  as i understood from this post: </p>
  
  <p><a href="https://stackoverflow.com/questions/23845639/are-all-the-web-requests-executed-in-parallel-and-handled-asynchronously">Are all the web requests executed in parallel and handled asynchronously?</a></p>
  
  <p>A <strong>webApi</strong> service, by default, executes all its incoming requests in parallel, <strong>but only</strong> if the <strong>current multiple requests</strong> (at a certain time) came from <strong>different sessions.</strong>
  That is to say, if single client will send some <strong>simultaneously</strong> requests to server, all of them will be executed <strong>sequentially</strong> and won't be <strong>executed concurrently</strong>.</p>
  
  <p>This behavior is a real <strong>problem</strong> for us, because in some cases, our client sends bunch of requests from different client's listeners, asynchronously (by browser), and all of them will actually be <strong>queued</strong> instead of being <strong>executed concurrently</strong> at the server. Therefore, in some cases, we experiencing a <strong>serious performance issues</strong> which are really noticeable at the client's web page.</p>
  
  <p>How can we solve this problem?
  I understand we can maybe  <strong>disable session state</strong> but that isn't a normal thing to do.</p>