On Tue, Oct 15, 2019 at 9:34 AM Black Michael via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > > NetworkMessage.hpp -- several places. Though after reading some more descriptions it does seem to free flow back and forth as to who is client and who is server. The message aggregator is referred to as a server....not sure why....in my book a server is the one piece that can run by itself....clients aren't required. Clients are useless without the server. I think the code comments were written to be very generic as the client/server relationship is very much message specific to In/Out. UDP protocol doesn't really have a cliient/server architecture...just a protocol that rides on it. You could just as well replace client/server with "program and another program". >
This is what tripped me up as well. I didn't find the code or description to be wrong. It's fairly clear about client and server roles. It just never points out that wsjt-x is a 'client', and it's easy to miss that, since the UI says 'UDP Server.' mike, kj6vcp
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
