On 30/01/2016 23:49, Laurie, VK3AMA wrote:
JTAlert needs to reply with the schema number matching that sent from
WSJT-X in the first heartbeat packet or a lower number if not coded to
support the max schema received.
Hi Laurie,
that's correct and it should also keep watching the "Maximum schema
number" field as the schema number may decrease due to some other node,
say an old version of another server, joins the network and cannot cope
with the currently negotiated schema. This dynamic behaviour can be
probably be ignored if the server is not multicast UDP since that
precludes other servers joining but that is not advised as it will
potentially block other users of the UDP message protocol.
I understand that coding for old schemes in new code is potentially
tricky but that is the price of supporting a heterogeneous UDP protocol.
73
Bill
G4WJS.
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
