Re: [Hamlib-stationserver] Sharing a radio between multiple applications
Library to control radio transceivers and receivers
Brought to you by:
n0nb
From: Art B. <ac...@in...> - 2014-03-04 21:02:10
|
True that! It's somewhat easier on the network, as network interfaces tend to support messages/events better than the internal APIs of many languages and OSs - Art On Mar 4, 2014, at 12:55 PM, Tony Langdon <vk...@gm...> wrote: > On 5/03/2014 7:33 AM, Art Botterell wrote: >> Got it... multiple simultaneous clients for control, content or both. I'll add that. > Yep. The current situation with rig control brings back nasty memories > of DOS networking, and attempting to use the same network interface from > multiple applications simultaneously (under DESQview). And even with > the shim that was supposed to make it work, it was about as stable as a > house of cards in a hurricane. :) Also brings back memories of Wordstar > and Word Perfect in DOS, where the application had to have its own > driver for the printer (like today's control applications have to > support the radio, rather than using an abstraction). > > Upgrading to OS/2 20 years ago, and later Linux and Windows was a breath > of fresh air, on this front (though Windows had many other issues that > took longer to be addressed). > > -- > 73 de Tony VK3JED/VK3IRL > http://vkradio.com > > > ------------------------------------------------------------------------------ > Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. > With Perforce, you get hassle-free workflows. Merge that actually works. > Faster operations. Version large binaries. Built-in WAN optimization and the > freedom to use Git, Perforce or both. Make the move to Perforce. > http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk > _______________________________________________ > Hamlib-stationserver mailing list > Ham...@li... > https://lists.sourceforge.net/lists/listinfo/hamlib-stationserver |