summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorBlacker1230 <blacker1230@163.com>2022-04-01 17:41:57 +0800
committerJens Geyer <Jens-G@users.noreply.github.com>2022-04-01 18:53:15 +0200
commit15cc0c4da218a375cadc67e541a99fdc6c5083f2 (patch)
tree363eae02ab88e8f9ec6cef79ebe2260b50f93395 /doc
parente165fa3c85d00cb984f4d9635ed60909a1266ce1 (diff)
downloadthrift-15cc0c4da218a375cadc67e541a99fdc6c5083f2.tar.gz
fix binary protocol's first byte value.
Diffstat (limited to 'doc')
-rw-r--r--doc/specs/thrift-rpc.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/specs/thrift-rpc.md b/doc/specs/thrift-rpc.md
index fbff3b6a1..a18d10400 100644
--- a/doc/specs/thrift-rpc.md
+++ b/doc/specs/thrift-rpc.md
@@ -151,7 +151,7 @@ always slightly faster.
## Compatibility
A server could automatically determine whether a client talks the binary protocol or the compact protocol by
-investigating the first byte. If the value is `1000 0001` or `0000 0000` (assuming a name shorter than ±16 MB) it is the
+investigating the first byte. If the value is `1000 0000` or `0000 0000` (assuming a name shorter than ±16 MB) it is the
binary protocol. When the value is `1000 0010` it is talking the compact protocol.
## Framed vs. unframed transport