title: CrmServiceClient reuse or connection pooling in Web Api project
body: <p>I am trying to understand how to use CrmServiceClient of the CRM SDK in a Web Api project and want to confirm if my understanding is correct.</p>
  
  <p>Is it true that CrmServiceClient implements connection pooling? If so, is it valid to simply create a new instance per web-request as the overhead of creating a new connection will be mitigated by CrmServiceClient?</p>
  
  <p>Or should I use a single instance of CrmServiceClient throughout the entire application? I don't think this works because my understanding is it is not thread safe and eventually the connection will close (I think). </p>