w4kek/WSJT-X
1
0
Fork 0
mirror of https://github.com/saitohirga/WSJT-X.git synced 2024-12-25 20:33:08 -05:00
Code Issues Packages Projects Releases Wiki Activity

Clarify UDP network message schema negotiation prior to schema 3

Browse Source 
Before schema  3 the Heartbeat(0)  message did not contain  a "Maximum
schema  number" field,  this field  being absent  implies that  schema
number 2 is the highest usable (schema 1 is broken and not used in the
field).

git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@6450 ab8295b8-cf94-4d9e-aec4-7959e3be5d79
This commit is contained in:
Bill Somerville 2016-01-31 00:07:42 +00:00
parent d736187107
commit ef8c2ad0bb
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
NetworkMessage.hpp
View File

@ -98,6 +98,11 @@
* that number shall be used for all further outgoing messages from * that number shall be used for all further outgoing messages from
* either clients or the server itself. * either clients or the server itself.
* *
* Note: the "Maximum schema number" field was introduced at the
* same time as schema 3, therefore servers and clients must assume
* schema 2 is the highest schema number supported if the Heartbeat
* message does not contain the "Maximum schema number" field.
*
* *
* Status Out 1 quint32 * Status Out 1 quint32
* Id (unique key) utf8 * Id (unique key) utf8