From 8aaa5fe996e44a0c68c069b8e70649264f5e8a56 Mon Sep 17 00:00:00 2001 From: irungentoo Date: Fri, 28 Mar 2014 22:37:42 -0400 Subject: TCP server almost ready. --- docs/TCP_Network.txt | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'docs') diff --git a/docs/TCP_Network.txt b/docs/TCP_Network.txt index 80cdfbdb..ee1bcbde 100644 --- a/docs/TCP_Network.txt +++ b/docs/TCP_Network.txt @@ -100,6 +100,10 @@ special ids and packets: [uint8_t id (2)][uint8_t (packet id of connection that got connected)] 3 - Disconnect notification: [uint8_t id (3)][uint8_t (packet id of connection that got disconnected)] +4 - ping packet +[uint8_t id (4)][uint64_t ping_id] +5 - ping response (pong) +[uint8_t id (5)][uint64_t ping_id] 8 - onion packet (same format as initial onion packet (See: Prevent tracking.txt) but packet id is 8 instead of 128) 9 - onion packet response (same format as onion packet with id 142 but id is 9 @@ -129,6 +133,13 @@ If the server receives an onion packet he handles it the same as he would if it was one received normally via UDP, he must also assure himself that any responses must be sent to the proper client. +Ping responses must have the same ping_id as the request. + +If the server recieves a ping packet he must respond with a ping response. + +The server will send a ping packet to clients every 30 seconds, they have 30 +seconds to respond, if they don't the connection is deleted. + Client: Implementation details coming soon. -- cgit v1.2.3