On 05/12/2015 00:24, Laurie, VK3AMA wrote:
The only reason that JTAlert is not using multi-cast is due to limitations of the current JTAlert Compiler/Language. One of many reasons (not to mention lack of multi-threading and async functionalities) that JTAlert is being rewritten.
Understood Laurie, that is quite reasonable and currently since there are few applications that use the UDP messages from WSJT-X it is not a serious deficiency. Your choice to require that each WSJT-X instance send to a different service port is a consequence of multiple instances of JTAlert combined with limitations of your development tool set.

I just wanted to clarify that if possible those writing applications that use the WSJT-X UDP protocol should support multicast UDP so as not to block or be blocked by cooperating applications from other authors.

73
Bill
G4WJS.
------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to