nitox
nitox copied to clipboard
66Origin
Tokio-based async NATS client
Is there a way to configure what happens when the server sends a 'slow consumer' notification? I've noticed that the subscription to a topic will remain active, even if there's...
I observed some very interesting behavior while using this crate in a few services of mine. I've observed that running multiple tasks on the tokio runtime along with a nitox...
It looks like Nitox doesn't support client verification as of now. I made [some quick changes](https://github.com/Naamio/nitox/commit/7b12744b0b8f313aceb3a5c6182fd115154a9170) to pass TLS config to the `native-tls` connector. When I tested this, I'm getting:...
Closes #27 - [ ] Add optional client cert options for mutual authentication - [ ] Give proper errors when supplying cluster URI (needs to tell that TLS needs a...
Still some work needed on this. It pretty much is done, except ending up the support for `verbose` mode which is 3/4 done. Needs integration tests against a STAN server.
Hey all, I've been doing some hacking on this lib and noticed this issue during development. Looks like it is closely related to #6, though I am not building new...
As described in the Nats [FAQ here](https://nats.io/documentation/faq/#a-name-reqvspub-a-what-is-the-difference-between-request-and-publish), it is assumed that users should be able to specify timeouts when making requests (request/response pattern). We can use [tokio's timeout system](https://docs.rs/tokio/0.1/tokio/timer/struct.Timeout.html) to...
NATS clients should be able to support the > 2.0 authentication mechanism that uses nkeys. [Here](https://github.com/nats-io/go-nats#new-authentication-nkeys-and-user-credentials) is an example of what it looks like in Go)
