Skip to content

Commit a59fcd6

Browse files
committed
PROTOCOL.md: update message frame maximum data length.
Update maximum data length in a message frame and reserved most significant byte to be a reserved most significant bit. Signed-off-by: Krisztian Litkey <[email protected]>
1 parent e61baa0 commit a59fcd6

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

PROTOCOL.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -42,9 +42,9 @@ use is defined by the message type.
4242

4343
The Data Length field represents the number of bytes in the Data field. The
4444
total frame size will always be Data Length + 10 bytes. The maximum data length
45-
is 4MB and any larger size should be rejected. Due to the maximum data size
46-
being less than 16MB, the first frame byte should always be zero. This first
47-
byte should be considered reserved for future use.
45+
is limited to the largest positive 32-bit signed integer. Therefore the most
46+
signficant bit should always be zero. This bit should be considered reserved
47+
for future use.
4848

4949
The Stream ID must be odd for client initiated streams and even for server
5050
initiated streams. Server initiated streams are not currently supported.

0 commit comments

Comments
 (0)