Colin Sullivan

Apologies for the delay. To be honest, I don't think the performance benefits will outweigh the changes to the existing client, and the current event handlers are designed to block...

@mullerch , thank you so much for the provided test and detail in this issue. Much appreciated! We'll take a look.

Apologies @jasper-d , I forgot about your issue https://github.com/nats-io/nats.net/issues/352 when I opened this.

Sorry to see you closed this - there were a lot of good changes here... (and I did recently fix TestAsyncInfoProtocolPrune).

Not sure if it'll help, but IIRC for mac/linux local testing I had to create a softlink... nats-server.exe -> nats-server - a hack... e.g. ```$ ls -arlt `which nats-server.exe` lrwxr-xr-x...

@Sergey-Terekhin , thanks for raising this issue. I did verify that locally the 0.11.0 client can connect to a NATS server v2.1.9. It's looking like the stream reader returned null,...

There is an bug here where we need to gracefully throw a connection exception when the stream reader returns a null (indicating EOS). When this happens, we might also want...

I believe this is resolved in #432.

To be honest, I haven't tried but am not aware of any limitations that would prevent it - will give it a shot. If anyone in the NATS ecosystem has...

I've looked into this. It works server-side, but not client side. Client-side, the browser running WASM sandboxed, so the NATS client isn't allowed to create a TCP connection to the...