Changes between Version 3 and Version 4 of NetworkProtocol
- Timestamp:
- 03/24/14 05:33:18 (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
NetworkProtocol
v3 v4 6 6 * General packets that flow in both direction: 7 7 ||= Packet Type =||= Arguments =||= Purpose =||= Actions Required =|| 8 ||hello||a dictionary containing connection options ||authentication (if required), setup of keyboard, configuration options, etc||either accept the connection and send a hello back as acknowledgement, send a challenge request or disconnect||8 ||hello||a dictionary containing connection options and capabilities||authentication (if required), setup of keyboard, configuration options, etc||either accept the connection and send a hello back as acknowledgement, send a challenge request or disconnect|| 9 9 ||ping||time to be echoed back||monitor connection state, collect latency statistics||The receiver ''must'' send a {{{ping-echo}}} back|| 10 10 ||ping-echo||echoed time, load average, measured latency||response to ping||none, it ''should'' be used to collect latency statistics|| … … 12 12 ||connection-lost||none||sent by the network layer when the network connection has dropped||free any resources|| 13 13 ||gibberish||none||sent by the network layer when the network received unparseable data, data decompression failed or decryption failed||disconnect the connection and free any resources|| 14 }}} 14 15 * Packets sent by the server 16 ||= Packet Type =||= Arguments =||= Purpose =||= Actions Required =||= Client Capability Required =|| 17 ||startup-complete||none||notifies the client that all the windows have been sent||none||notify-startup-complete|| 18 ||new-window||many!||tells the client to create a new window||the client ''should'' show the new window, it should eventually send a {{{map-window}}} packet with the location of the window||none||