Re: [Hamlib-stationserver] Domain Object Outline: What's in a Station?

[Art B. <ac...@in...>]

On Mar 7, 2014, at 4:09 AM, Nate Bargmann <n0...@n0...> wrote
> I will note that there
> will be requests for certain device specific readings/settings and
> provision will need to be made for that.

Right... those are the CONTROL and READING objects down at the bottom, which in addition to their use inside higher-level device definitions could be instantiated independently to access whatever gizmos a particular station has on offer.

This is a bit of a slippery slope, of course.  If we think station users are going to insist on mapping their particular rig's physical UI literally to the network view, we might as well call it a day on abstraction and simply slap a web-service facade on each of the hamlib back-ends.  

And if we're only concerned with the single-user application that might well be the case.  The benefits of abstraction come when folks try to operate equipment they aren't familiar with in detail... "interoperability" at the User level.

- Art KD6O