🚀 go-pugleaf

> Unless you want to deal with configuring DCOM for remote access, as well
as
> the OS for user access rights, then using a TCP socket is fine.
>

Is configuring DCOM for remote users tricky?
What is involved in configuring the OS for user acces rights?

Would the user notice the difference in whichever way I select?  I suppose
my underlying queries are in knowing how the end users would see the
interaction between configuration application and service application using
either DCOM or TCP Socket.

> Since the client already has direct access to the database, how about
> storing the configuration in a database instead of a file?  Then the
client
> can configure the service by editing the database and not communicate with
> the service at all.

Part of the configuration of the Service was to nominate where and what type
of database is used, also, in some situations there will be no database (I
forgot mention this earlier), therefore I have to keep the configuration
away from being stored in the DB.  The client Data Display application will
only be used in those situations where there is a DB used - which is part of
the reason for having a seperate configuration application.


Thanks for your feedback, i've been appreciating your insights and
questions..