izaya/OC-Copper
1
0
Fork 0
mirror of https://github.com/XeonSquared/OC-Copper.git synced 2024-11-23 01:48:06 +11:00
Code Issues Releases Wiki Activity

Update protocol.0

Browse Source
This commit is contained in:
20kdc 2017-08-16 15:37:33 +01:00 committed by GitHub
parent 120934483c
commit de672239be
1 changed files with 9 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
protocol.0
View File

@ -22,8 +22,10 @@ A name (as a length-minus-1-byte-prefixed-string),
another name (in the same format), another name (in the same format),
and the rest is data. and the rest is data.
Copper packet data may be up to 1506 bytes long - Copper packet data may be up to 1507 bytes long.
this does not include header data, which may be up to (256*2) + 3 bytes long. 1500 in-relib data bytes + 7 relib bytes.
This makes the user's life easier by having an easy to remember MTU from within relib of 1500 bytes.
This does not include header data, which may be up to (256*2) + 3 bytes long.
Loop detection should performed by checking if a packet exactly the same has Loop detection should performed by checking if a packet exactly the same has
been seen recently - other rejection, alteration and routing measures been seen recently - other rejection, alteration and routing measures
@ -84,3 +86,8 @@ The connection between OpenComputers and Copper can be performed with a TCP gate
It doesn't really matter how the data is transmitted here, since it's just a gateway. It doesn't really matter how the data is transmitted here, since it's just a gateway.
Possibly consider integrating a hierarchial gateway into the OpenComputers/world bridge. Possibly consider integrating a hierarchial gateway into the OpenComputers/world bridge.
ERRATA:
The data MTU was described as 1506 bytes due to an error in the protocol.2 document.
It should be 1507 to fit 1500 relib byets and the 7-byte header.