Re: [Hamlib-stationserver] Sharing a radio between multiple applications

[Tony L. <vk...@gm...>]

On 4/03/2014 12:48 PM, Art Botterell wrote:
> Thanks, Tony, lot's to chew on, there.  Hope you don't mind if I tease out some individual threads.
>
> For starters... I'm not sure I totally grasp what you have in mind about "sharing of a radio between multiple applications."  Do you mean multiple clients, or multiple server threads, or something else?
>
> Could you help me with an example of what you mean?
Multiple clients - for example, I may have dl-fldigi decoding telemetry 
on the shack PC, but am sitting in another room with HRD keeping an eye 
on the VFO frequency, or even another copy of fldigi, to keep an eye on 
the waterfall and making sure it's centred.

Or I might have a remote base module loaded, and want to locally take 
over the radio, while remote base users are free to log in and listen.

RMS Express is another good example.  As it stands, it's good in that 
when you close a session, it returns the VFO back to where it was, but 
with applications able to share, RMS Express could go further...  When 
you start the session, it still remembers the previous VFO frequency, 
but then it takes exclusive control of the radio, runs a mail session 
and when you end, returns the VFO and releases exclusive control, 
without having to unload anything else.

Could also make things easier for the ALE operators who also run a 
WINMOR based BBS.  How this works normally is you send a text to the BBS 
on ALE then start a RMS Express session, but I think you have to jump 
through some hoops to make it work with current architectures. With the 
radio server, it should be a breeze.

Trying to avoid the having to unload one application to load another 
scenario, which becomes a real pain when dealing with multiple machines :)

-- 
73 de Tony VK3JED/VK3IRL
http://vkradio.com