Quickly return for no responders

[autodidaddict]

It looks like the only result code from making requests on a topic is :timeout. Does this apply to when there are no responders (which NATS immediately replies with)? If not, could we get some way to indicate the difference between when we waited the full timeout period versus when we waited no time due to lack of responders?

[mmmries]

@autodidaddict I didn't know about NATS providing a "no responders" message. Do you have a link to the documentation that shows this?

I would love to provide an immediate feedback that differentiates the two cases, but I think currently the code is just always waiting for the timeout and not paying attention to the message from NATS

[autodidaddict]

https://github.com/nats-io/nats.rs/search?q=no+responders

[autodidaddict]

Both the Rust and Go clients immediately short-circuit when there are no responders.

[autodidaddict]

https://github.com/nats-io/nats.go/search?q=no+responders

[mmmries]

Perfect thanks for those links. I'll take a look and see if we can get the same thing implemented for our elixir client ❤️ 💛 💙 💚 💜

[autodidaddict]

I went looking for actual documentation and, unsurprisingly, I couldn't find this feature documented anywhere. Lately I just go to the source code because I have little confidence in the docs.

[mmmries]

Released in version 1.6.0 🎉 https://hex.pm/packages/gnat/1.6.0