nats
nats copied to clipboard
jgaskins
NATS client in pure Crystal with JetStream support
There were interchangeable uses of "message", "body", and "data" referring to the message payload data. This change conforms to the [NATS protocol](https://docs.nats.io/reference/reference-protocols/nats-protocol#msg) which uses "message" as the encompassing message (headers...
Firstly, sorry for the several issues. really digging deep here. Thanks for the library! NATS headers allows duplicate keys with different values, just like HTTP headers (the server might have...
from the nats doc, we can specify an optional client name to the connection https://docs.nats.io/reference/reference-protocols/nats-protocol#syntax-1 i went through the code in this repo and found out this is achievable by...
I have this code in my crystal client to check the state of the connection: ```crystal nats = NATS::Client.new(URI.parse("nats://127.0.0.1:4222")) puts "NATS server_info: #{nats.server_info}" nats.on_disconnect { puts "NATS disconnected!" } spawn...
The folks at Synadia have [written about sending one request and receiving many replies](https://www.synadia.com/blog/orbit-and-the-future-of-the-clients). There are several use cases for this: - Chunked responses, such as [fetching object contents from...
This will need to be a process rather than a one-and-done task. The `body` method is used everywhere and we should assume that users are also using it. So the...