Ivan Kozlovic

@derekcollison The choice was made to have js.Subscribe() possible create the consumer, and also delete it. As you may remember, I was against this idea. Right now, we have explained...

We don't delete the one we "bound" to.. But imagine this: no JS consumer currently exists. User calls `js.Subscribe("foo", nats.Durable("dur"))`, the library will not find such durable and then call...

But it was decided that the library would work this way (see ADR-15). Again, I personally don't like it, but currently it works as designed. The question and reason we...

A durable is different from ephemeral in that ephemeral is R1 only, while a durable can be Rn, which would allow to survive a node failure and durable would still...

@Ja7ad Thank you for your contribution. However, we have internally said that the encoded connection in core NATS that was introduced long ago, was maybe not the best choice. So...

Few comments: I do think that there is a value for being able to flush the socket buffer on each write. For instance, when writing the C Client, I did...

About `nc.conn == nil`, actually I am wrong. It will happen when disconnected and trying to reconnect. But I guess you have a different meaning than I chose for the...

@sgof1d Would you have a test case that reproduce this? The pool implementation does the right thing, I believe, in that when putting it back to the pool it stops...

I think I have seen some issue reports around that. Will try to reproduce with using simple timer/pool but outside of NATS and see... out of curiosity, which platform are...

My guess would be the use of gollvm instead of go.