Difference between revisions of "Talk:Message"
Dale Innis (talk | contribs) (New section: Four-byte IP addresses?) |
(→Variable 2 Data Type Endian: new section) |
||
| Line 6: | Line 6: | ||
"IPADDR - IP Address, one place per byte, 4 bytes wide": is there a page anywhere talking about possible / future / current / lack of support for IPv6? (16-byte addresses) -- [[User:Dale Innis|Dale Innis]] 12:14, 19 February 2008 (PST) | "IPADDR - IP Address, one place per byte, 4 bytes wide": is there a page anywhere talking about possible / future / current / lack of support for IPv6? (16-byte addresses) -- [[User:Dale Innis|Dale Innis]] 12:14, 19 February 2008 (PST) | ||
== Variable 2 Data Type Endian == | |||
It says, that the endian of the first two bytes that determine the size of the Variable 2 Type (Size U16), is big-endian. But it is actually a little-endian! | |||
Revision as of 11:04, 26 February 2016
Am I missing something on the very first page I read (/me sighs) or is the Message Format example wrong? Shouldn't it be "multiple 3" or maybe have a 4th NeighborBlock or be "variable"?
So the message format example was pulled directly from the message template, so it works (even though it's never used, just there to test the parser). However, the message format [i]description[/i] was off, as variable shouldn't have a number after it for block sizes (that's added to the message on creation). Fixed that.
Four-byte IP addresses?
"IPADDR - IP Address, one place per byte, 4 bytes wide": is there a page anywhere talking about possible / future / current / lack of support for IPv6? (16-byte addresses) -- Dale Innis 12:14, 19 February 2008 (PST)
Variable 2 Data Type Endian
It says, that the endian of the first two bytes that determine the size of the Variable 2 Type (Size U16), is big-endian. But it is actually a little-endian!