You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All the packets below have a common structure that is not clear from the description. Every DHT packet looks the same, but with a different payload. In the case of a ping packet, the payload is the ping id. Repeating the entire DHT packet structure hides this commonality.
The text was updated successfully, but these errors were encountered:
iphydf
changed the title
All the packets below have a common structure that [...]
[DHT] All the packets below have a common structure that [...]
Oct 12, 2015
iphydf
changed the title
[DHT] All the packets below have a common structure that [...]
[DHT] All the packets below have a common structure that is not clear from the description. [...]
Oct 20, 2015
Instead of writing the same packet format several times, with only the payload different, write it once, give it a name, and then describe the possible payloads. You don't write the IP header and UDP header every time, either. It's defined once, and then you have: NodesResponse in DHT-packet in UDP packet in IP packet in Ethernet frame(s) (or similar).
https://github.com/Tox-Docs/Text/blob/master/src_text/DHT.txt#L21
Comment on
found at column 1.
All the packets below have a common structure that is not clear from the description. Every DHT packet looks the same, but with a different payload. In the case of a ping packet, the payload is the ping id. Repeating the entire DHT packet structure hides this commonality.
The text was updated successfully, but these errors were encountered: