Should I create new HttpClient for each new request?

Question

I've got and rest api class that has several methods that perform http requests to my service. In constructor it create instance of HttpClient. Api instance is reused in different threads. Will it cause cross thread problems?

Currently i see two ways to make it thread safe:

Create new http client for each request.
Create separate instances of api class for each thread.

You can use synchronize method for remove cross thread problems. — Dharmendra, Aug 27 '11 at 07:08
Yep. I know. But from .NET experience it is not a good practice. — Alexey Zakharov, Aug 27 '11 at 07:15
Does this answer your question? [What is the overhead of creating a new HttpClient per call in a WebAPI client?](https://stackoverflow.com/questions/22560971/what-is-the-overhead-of-creating-a-new-httpclient-per-call-in-a-webapi-client) — Michael Freidgeim, Aug 09 '21 at 02:50

score 2 · Accepted Answer · edited May 23 '17 at 12:12

I had an answer to a similar question that may help. I basically use:

// Should be thread safe
public class HttpClientFactory {

            private static DefaultHttpClient client;

            public synchronized static DefaultHttpClient getThreadSafeClient() {
                    if (client != null)
                            return client;
                    client = new DefaultHttpClient();
                    ClientConnectionManager mgr = client.getConnectionManager();
                    HttpParams params = client.getParams();
                    client = new DefaultHttpClient(new ThreadSafeClientConnManager(params,
                                    mgr.getSchemeRegistry()), params);
                return client;

            }
    }

The question has the full posting.

Should I create new HttpClient for each new request?

1 Answers1