reemo/sockscape
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

this probably won't work

Browse source 
or maybe it will
This commit is contained in:
Malloc of Kuzkycyziklistan 2017-05-16 08:33:32 -05:00
parent f39c11847c
commit 645a2eb9d0
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
protocol.md
View file

@ -10,7 +10,7 @@ All references to the 'byte' in this document refers to individual 8-bit octets,
Because the body of the packet is a sequence of many different regions of byte data that is not delimited, it is necessary for the header of the packet to determine boundaries for the regions of data. Because the body of the packet is a sequence of many different regions of byte data that is not delimited, it is necessary for the header of the packet to determine boundaries for the regions of data.
* The first byte is the packet id, the necessary ones of which are defined in the _BODY_ section. * The first byte is the packet id, the necessary ones of which are defined in the [_Packet IDs_](#packet-ids) section.
* The second byte is the number of byte regions in the packet. * The second byte is the number of byte regions in the packet.
* The bytes following the second byte are a list of binary length segments, each of which correspond to the number of bytes in its respective region. They each follow this format: * The bytes following the second byte are a list of binary length segments, each of which correspond to the number of bytes in its respective region. They each follow this format:
* If length is less than 254, the length of the region is stored in a single byte. * If length is less than 254, the length of the region is stored in a single byte.
@ -25,7 +25,7 @@ The message body immediately follows the header with no separator, and consists
### Numeric Packing ### Numeric Packing
All numbers, unless otherwise specified here or in the _BODY_ section, are the string representation of a base 10 number. Common exceptions below: All numbers, unless otherwise specified, are the string representation of a base 10 number. Common exceptions are listed below:
* User IDs: 8 bytes, integer, unsigned * User IDs: 8 bytes, integer, unsigned
* Co-ordinates: 8 bytes, double-precision float * Co-ordinates: 8 bytes, double-precision float