taigrr/nats.docs
1
0
Fork 0
mirror of https://github.com/taigrr/nats.docs synced 2025-01-18 04:03:23 -08:00
Code Issues Projects Releases Wiki Activity

Fixing links (all lower chase anchors and removing github links)

Browse Source 
Signed-off-by: Matthias Hanel <mh@synadia.com>
This commit is contained in:
Matthias Hanel
2020-04-13 16:22:10 -04:00
parent ceace00a26
commit 9443b0ced5
17 changed files with 38 additions and 38 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
nats-protocol/nats-protocol/nats-client-dev.md
View File

@@ -62,7 +62,7 @@ NATS implements auto-pruning. When a client connects to the server, the server e
## Parsing the protocol
NATS provides a text-based message format. The text-based [protocol](https://github.com/nats-io/nats.docs/tree/51fc56e3090645f7cedb242415e2d5361e1807e7/documentation/internals/nats-protocol/README.md) makes it easy to implement NATS clients. The key consideration is deciding on a parsing strategy.
NATS provides a text-based message format. The text-based [protocol](README.md) makes it easy to implement NATS clients. The key consideration is deciding on a parsing strategy.
The NATS server implements a [zero allocation byte parser](https://youtu.be/ylRKac5kSOk?t=10m46s) that is fast and efficient. Off the wire, a NATS message is simply a slice of bytes. Across the wire the message is transported as an immutable string over a TCP connection. It is up to the client to implement logic to parse the message.