Re: [Hamlib-stationserver] Updated Requirements Doc
Library to control radio transceivers and receivers
Brought to you by:
n0nb
From: Tony L. <vk...@gm...> - 2014-03-06 22:15:55
|
On 7/03/2014 2:07 AM, Art Botterell wrote: > A small update is online at <http://sourceforge.net/projects/hamlib/files/stationserver/documents/requirements/StationServer%20Requirements%20DRAFT%202.pdf/download> > > I hope everyone who can will take a few minutes to look it over and comment. The thing that caught my eye here was the reference to multiple users. I don't believe it's the job of Stationserver to handle multiple users. I envisaged it as a single user system, with multiple user capabilities being provided by an add-on, such as a remote base add-on, which would handle all the multiple user requirements such as authentication and access control. Thinking again though, there may be a use for a (very basic) user authentication mechanism. The question is whether this is best implemented by default (which would be a nuisance for a single user shack, and especially annoying in the case of someone who runs clients and servers on the one PC - though localhost could always be given permission), as an optional switch or as an add-on. I'm somewhere between not having multiuser capability in the core product or having it available via a configuration option, and only a basic set of access controls at this level. One of the assumptions here is that one entity still manages the entire system - whether that be an individual or a club, and there is a reasonable expectation of a degree of trust and personal knowledge of the users (i.e. regularly in face to face contact and can be personally validated). If this trust isn't there, then we have a remote base situation. -- 73 de Tony VK3JED/VK3IRL http://vkradio.com |