Skip to content

clarify byte ordering #546

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: local_loop_prototype
Choose a base branch
from
+4 −0
Open

clarify byte ordering #546

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions external_parser/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,10 @@ The general format of each message is shown in this table. Details for each mess
| `payload_size` | payload content (required if not inline payload) |
| `payload_size % 8` | padding (required if not inline payload) |

### Byte ordering

The byte order for message type identifier and payload size must be little-endian. The payload itself can be message type defined, but since all messages are either empty or flatbuffers (which are themselves little-endian) in practice this means the payload is also little-endian.

### Message type
The first 4 bytes in each message is an unique indentifier:
- `MSG_TYPE_FILEMAGIC = 0x42465756` (in ASCII this is `VWFB`)
Expand Down