From f82912c90f087cb2b209e5485b1c7a16543bcff4 Mon Sep 17 00:00:00 2001 From: Bill Somerville Date: Sun, 31 Jan 2016 00:07:42 +0000 Subject: [PATCH] Clarify UDP network message schema negotiation prior to schema 3 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 --- NetworkMessage.hpp | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/NetworkMessage.hpp b/NetworkMessage.hpp index c638dadfc..14fdb1e30 100644 --- a/NetworkMessage.hpp +++ b/NetworkMessage.hpp @@ -98,6 +98,11 @@ * that number shall be used for all further outgoing messages from * 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 * Id (unique key) utf8