From a6d9680411075ed4b3bf4bc8095406c52aadac0d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E6=9E=97=E5=BF=97=E5=AE=87?= Date: Wed, 19 Jun 2019 15:42:49 +0800 Subject: [PATCH] Fix dmsg documentation. --- pkg/dmsg/README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/pkg/dmsg/README.md b/pkg/dmsg/README.md index b9f18ad174..e845548b69 100644 --- a/pkg/dmsg/README.md +++ b/pkg/dmsg/README.md @@ -77,12 +77,12 @@ The following is a summary of the frame types: Transports are represented by transport IDs and facilitate duplex communication between two `dmsg.Client`s which are connected to a common `dmsg.Server`. Transport IDs are assigned in such a manner: -- A `dmsg.Client` manages the assignment of positive transport IDs between itself and each connected `dmsg.Server`. The set of transport IDs will be unique between itself and each `dmsg.Server`. -- A `dmsg.Server` manages the assignment of negative transport IDs between itself and each connected `dmsg.Client`. The set of transport IDs will be unique between itself and each `dmsg.Client`. +- A `dmsg.Client` manages the assignment of even transport IDs between itself and each connected `dmsg.Server`. The set of transport IDs will be unique between itself and each `dmsg.Server`. +- A `dmsg.Server` manages the assignment of odd transport IDs between itself and each connected `dmsg.Client`. The set of transport IDs will be unique between itself and each `dmsg.Client`. For a given transport: -- Between the initiating client and the common server - the transport ID is always a positive value. -- Between the responding client and the common server - the transport ID is always a negative value. +- Between the initiating client and the common server - the transport ID is always a even value. +- Between the responding client and the common server - the transport ID is always a odd value. Hence, a transport in it's entirety, is represented by 2 transport IDs.