On 10/06/2016 13:24, Black Michael wrote:
One possible solution is a simple ack/nak packet.
Hi Mike,that doesn't really sit well with the fire and forget nature of UDP messages. Once you start adding conversational protocols you might as well use TCP/IP but that requires asynchronous processing or threads and a whole lot of state for each "client". The current UDP message infrastructure in WSJT-X is stateless at the connection level and synchronous, very simple and no waiting for network replies.
73 Bill G4WJS.
------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
