title: Do Windows.Web.Http.HttpClient have to be disposed per HTTP request?
body: <p>From this <a href="https://stackoverflow.com/a/15708633/700926">answer</a> to the question: <a href="https://stackoverflow.com/q/15705092/700926">Do HttpClient and HttpClientHandler have to be disposed?</a>, I see that the best practice is <em>not</em> to dispose a <code>System.Net.Http.HttpClient</code> per HTTP request. In particular, it is stated that:</p>
  
  <blockquote>
    <p>standard usage of HttpClient is not to dispose of it after every request.</p>
  </blockquote>
  
  <p>And that is fine.</p>
  
  <p>My question is, does this "pattern" apply to <code>Windows.Web.Http.HttpClient</code> as well? Or should it be disposed per HTTP request? I think the <a href="https://msdn.microsoft.com/library/windows/apps/dn298639" rel="nofollow noreferrer">documentation</a> is a bit vague on this. In one of the samples, it simply states:</p>
  
  <pre><code>// Once your app is done using the HttpClient object call dispose to 
  // free up system resources (the underlying socket and memory used for the object)
  httpclient.Dispose();
  </code></pre>
  
  <p>I believe this can be read both ways, so any specific input on this is appreciated.</p>