mirror of
https://github.com/taigrr/nats.docs
synced 2025-01-18 04:03:23 -08:00
dead links
This commit is contained in:
@@ -2,7 +2,7 @@
|
||||
|
||||
The wire protocol used to communicate between the NATS server and clients is a simple, text-based publish/subscribe style protocol. Clients connect to and communicate with `nats-server` (the NATS server) through a regular TCP/IP socket using a small set of protocol operations that are terminated by a new line.
|
||||
|
||||
Unlike traditional messaging systems that use a binary message format that require an API to consume, the text-based NATS protocol makes it easy to implement clients in a wide variety of programming and scripting languages. In fact, refer to the topic [NATS Protocol Demo](/documentation/internals/nats-protocol-demo/) to play with the NATS protocol for yourself using telnet.
|
||||
Unlike traditional messaging systems that use a binary message format that require an API to consume, the text-based NATS protocol makes it easy to implement clients in a wide variety of programming and scripting languages. In fact, refer to the topic [NATS Protocol Demo](nats-protocol-demo.md) to play with the NATS protocol for yourself using telnet.
|
||||
|
||||
The NATS server implements a [zero allocation byte parser](https://youtu.be/ylRKac5kSOk?t=10m46s) that is fast and efficient.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user