You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@thrift.apache.org by je...@apache.org on 2022/04/01 16:53:24 UTC
[thrift] branch master updated: fix binary protocol's first byte value.
This is an automated email from the ASF dual-hosted git repository.
jensg pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/thrift.git
The following commit(s) were added to refs/heads/master by this push:
new 15cc0c4 fix binary protocol's first byte value.
15cc0c4 is described below
commit 15cc0c4da218a375cadc67e541a99fdc6c5083f2
Author: Blacker1230 <bl...@163.com>
AuthorDate: Fri Apr 1 17:41:57 2022 +0800
fix binary protocol's first byte value.
---
doc/specs/thrift-rpc.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/specs/thrift-rpc.md b/doc/specs/thrift-rpc.md
index fbff3b6..a18d104 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