David Fowler

Thanks for the repro

davidfowl/dotnet-5 required RC1 bits https://github.com/dotnet/installer#installers-and-binaries

Abort is the way to disconnect the transport for sure.

Calling DisposeAsync to abort is incorrect. Calling Abort should work, if it doesn't work then there's a bug. DisposeAsync is implicitly called by the pipeline when the code unwinds.

@jkotalik I think there are different layers here: - The various parsers for message types (or single parser for multiple message types) - The crypto interface - The end to...

I prefer the latter. I'd like the crypto to be an abstraction though not baked to use open ssl.

I took a quick look and it does look quite promising. I'll take a deeper look and provide more detailed feedback.

@thenameless314159 have you tried to migrate the protocols in here to use your new APIs (especially the text based protocols)?

This is still alive and well. I plan to spend more time cleaning it up and polishing the API.

> I could create a singleton DI class to inject into ConnectionHandlers, and have each request call into that to store it's info, but I wouldn't get close notifications. Why...