Ivan Kozlovic

I guess I understand the want for using context.Context, but if it is really be able to set/get user values to/from the wrapper, would having a `Msg.UserValue interface{}` (I am...

@wallyqs I understand why we clear the Reply subject. I was just asking what other state is changed that justifies using a "copy" of the message. I am not saying...

Agreed that going the option way makes it more extensible and avoid explosion of APIs.

Right.. sorry, missed the fact that it has to be a different API for that one since the current Request() returns a message. We can't have return it nil but...

@derekcollison Do you think we should retry a few times here (https://github.com/nats-io/nats.go/blob/c157d64783d91fd2084064bd5c07a10dc4bba2d7/js.go#L1956) if we get an error (other than connection closed I guess)? Or is it ok to fail here...

@rampratapa I was asked to give some feedback. - Upgrade to latest NATS Streaming server: 0.18.0 - You probably need to bump the streaming client PingInterval/PingMaxOutstanding (although I see that...

> I read that the data is stored until the message limit reached or it expired ( if we set the TTL) Correct. I just wanted to make sure that...

We did implement Websocket in the Go client (and have nats.ws repo too). We will probably have to port websocket to all supported Synadia client libraries, it's just that it...

@dsidirop I noticed that you mentioned something about congestion control and should have picked on that. No, what we have currently in NATS Server (and some of the clients) is...

@dsidirop We probably need to update the roadmap, but what is there is QUIC (not WebTransport, which is different if I am not mistaken). Things have been moving quite a...