Closed jeremy001181 closed 5 years ago
This is by design. The pooling is done on the handler level, in a way similar to the HttpClientFactory. The client itself, is disposed similarly to package I mentioned.
Http handlers are cached for a specific amount of time using a concurrent friendly cache, so the costs of creation etc should be amortized in time.
Does it answer the question? If yes, please close, if not - please provide more evidence and/or background for this issue.
yes it does thank you
Would it have better performance by having a shared HttpClient object so that it reuses port for getting messages instead of allocate and dispose each time?
https://github.com/Scooletz/QueueBatch/blob/107e2f6447bd32203698cff9dd8a1aec7c2e0e21/src/QueueBatch/Impl/Queues/FastCloudQueue.cs#L118