I found this interesting, because I had just implemented a REST client that used a single HttpClient for its entire lifecycle, mostly for convenience. It's goo

I found this interesting, because I had just implemented a REST client that used a single HttpClient for its entire lifecycle, mostly for convenience. It's good to know I probably shouldn't go back through and change that design. IDisposable kind of sucks. Unless you know the inner workings of whatever implements it, it's hard to know how to handle lifecycles and how important properly disposing is. Is it wrapping a heavyweight COM object that is going to leak memory badly? Is it going to tie up limited system resources? Or is it a lightweight .NET object that someone has abused the interface to perform some trivial cleanup operations? There's no real guarantees.