Skip to content

Commit

Permalink
PROTOCOL.md: update message frame maximum data length.
Browse files Browse the repository at this point in the history
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 <krisztian.litkey@intel.com>
  • Loading branch information
klihub committed Aug 26, 2024
1 parent e61baa0 commit a59fcd6
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions PROTOCOL.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,9 +42,9 @@ use is defined by the message type.

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

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

0 comments on commit a59fcd6

Please sign in to comment.