Re:Using the .NET HttpClient class wrongly can destabilize s...
by artpepper on Tuesday August 30, 2016 @04:43PM
(#12393723)
I think the case that trips people up is using HttpClient in an ASP.NET MVC controller action. There, it doesn't look like a loop, but if you create/dispose on each request, you can get socket exhaustion under load.
[ Parent
| on HN ]
Re:Using the .NET HttpClient class wrongly can destabilize s...
by dogma1138 on Tuesday August 30, 2016 @05:26PM
(#12394052)
If that's the case you should use HTTP pipelining usually to bundle multiple requests via a single tcp connection.
https://en.m.wikipedia.org/wiki/HTTP_pipelining
Have it sitting in the background waiting for the controller to ask it to do something, you can manage the sockets and you can make a request queue on your end if you getting into resource cap issues.