Chris Dimitrov

@circler3 Thank you for your contribution. The change is generally safe to merge, but I will need some time to give it a test and review it locally. If everything...

Hello, @stevehayles , thank you for doing so. Currently, your link does not point to any branch, has it been deleted?

Great, thank you @stevehayles , looks good If that's okay for you, let's do a PR and merge it into the main repository.

@stevehayles Good point about Core 2.0. Not worried at all about 4.5.2 compatibility at this point in the development stage, and I doubt there will be an emerging demand for...

@NotoriousRebel @stevehayles Any concerns closing this task?

Hello! Confirming: this is not the package. I will soon document the installation process, and deploy it on NuGet, so that it’s easier. Thanks!

The issue is twofold from client to server and server to the client. Investigating.

@cate4cafe fixed with https://github.com/Vect0rZ/Quic.NET/commit/6e5c6146e2b1487f2905cd9895d2a04a40bc34d8

Good catch. We can use a NumberSpace class instance here, it's part of QuicNet.Infrastructure. We can substitute the streamId optional parameter with a private NumberSpace in the QuicClient, and leave...

Hello! This is something that I spend yesterday looking at it, you're absolutely right, it's currently not working, that is because the **Client** should not receive the data with a...