David Pine

We do have coverage of Pipelines, and it is discussed in the context of I/O and streams: - [System.IO.Pipelines in .NET](https://docs.microsoft.com/dotnet/standard/io/pipelines)

Hi @mlsomers It sounds like you're seeing socket exhaustion issues. As an alternative to `using var client = new HttpClient();`, which can lead to socket exhaustion, you should consider using...

> the next-steps branch has been merged into main. @IEvangelist you need resolve conflicts. I can't do it, it's in a repo of yours. Done...

Hey @jamesmontemagno - are we good to merge this one?

> @IEvangelist just changed to merge to main, can you re-validate stuff for me. Hey @jamesmontemagno - done

I believe this has been addressed, we've been using the .NET Version Sweeper to track out-of-support projects and updating them monthly. Closing this... https://github.com/dotnet/samples/issues?q=is%3Aissue+label%3Adotnet-target-version+is%3Aclosed

Closing this one as it is resolved by the user, and the existing API functions.

Closing this issue, as the matter of configuring serialization is the known solution.

That's an excellent observation. Would any of you be interested in working on addressing this issue?

No, immediate release timescale. Take your time, and this is much appreciated. Thank you.