2 54.6. Message Data Types #
4 This section describes the base data types used in messages.
7 An n-bit integer in network byte order (most significant byte
8 first). If i is specified it is the exact value that will
9 appear, otherwise the value is variable. Eg. Int16, Int32(42).
12 An array of k n-bit integers, each in network byte order. The
13 array length k is always determined by an earlier field in the
14 message. Eg. Int16[M].
17 A null-terminated string (C-style string). There is no specific
18 length limitation on strings. If s is specified it is the exact
19 value that will appear, otherwise the value is variable. Eg.
20 String, String("user").
24 There is no predefined limit on the length of a string that can
25 be returned by the backend. Good coding strategy for a frontend
26 is to use an expandable buffer so that anything that fits in
27 memory can be accepted. If that's not feasible, read the full
28 string and discard trailing characters that don't fit into your
32 Exactly n bytes. If the field width n is not a constant, it is
33 always determinable from an earlier field in the message. If c
34 is specified it is the exact value. Eg. Byte2, Byte1('\n').