summaryrefslogtreecommitdiff
path: root/doc/zmq_tcp.txt
diff options
context:
space:
mode:
authorMartin Lucina <mato@kotelna.sk>2010-09-04 15:54:34 +0200
committerMartin Lucina <mato@kotelna.sk>2010-09-04 15:54:34 +0200
commit6c393f53e28f41118eed9a8d034d8d46f2555572 (patch)
treef869eafd4488265bb456752ac01bb276029a3732 /doc/zmq_tcp.txt
parent6647e61243fdfbdc600ef3bfbd15b7c2ca6e853e (diff)
Revert "Further cleanups on reference manual"
This reverts commit 13f3481e127a6b2390e847af6b01ee88f1b4ae61. Conflicts: doc/zmq_device.txt doc/zmq_tcp.txt
Diffstat (limited to 'doc/zmq_tcp.txt')
-rw-r--r--doc/zmq_tcp.txt8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/zmq_tcp.txt b/doc/zmq_tcp.txt
index 2264d75..b96f3df 100644
--- a/doc/zmq_tcp.txt
+++ b/doc/zmq_tcp.txt
@@ -49,15 +49,15 @@ a colon and the TCP port number to use.
A 'peer address' may be specified by either of the following:
* The DNS name of the peer.
-* The IPv4 address of the peer, in its numeric representation.
+* The IPv4 address of the peer, in it's numeric representation.
WIRE FORMAT
-----------
0MQ messages are transmitted over TCP in frames consisting of an encoded
-'payload length', followed by a 'flags' field and the message body. The
-'payload length' is defined as the combined length in octets of the message
-body and the 'flags' field.
+'payload length', followed by a 'flags' field and the message body. The 'payload
+length' is defined as the combined length in octets of the message body and the
+'flags' field.
For frames with a 'payload length' not exceeding 254 octets, the 'payload
length' shall be encoded as a single octet. The minimum valid 'payload length'