title: .NET webservice call pooling?
body: <p>I am writing acceptance tests to validate a system and it's data access is all done through web service calls.</p>
  
  <p>Unfortunately, because I make so many calls, so quickly, I run into the following error</p>
  
  <blockquote>
    <p>System.Net.Sockets.SocketException:
    Only one usage of each socket address
    (protocol/network address/port) is
    normally permitted</p>
  </blockquote>
  
  <p>I have locally cached as many of the calls as possible, but that's not enough.  I can't fake or mock these calls.  They have to be real for this level of tests to be valid.</p>
  
  <p>Is there a way to get repeated frequent web service calls to pool?  </p>
  
  <p>Or to check if a connection can be made to the service prior to attempting the call, and wait until an available socket exists?</p>
  
  <p>In production the calls are never made at this speed, so the issue won't arise...but it would be nice to have some code in place to allow for the tests to work, and throttle or share the connections.</p>
  
  <p>Thanks</p>