🚀 go-pugleaf

My design thoughts are...

I want to install the service on a server/pc, then create an application
that will be used solely for configuring this service so that users don't
need to edit a raw ini file or registry, it would be preferable if this
config app can be run remotely as well as locally.

This service also pumps data into a database, so I don't need to obtain data
directly from the service as the Data Display application talks directly to
the database to get all it's data for users to filter and manipulate.

I don't require the configuration application to be part of the same client
application that displays the data within the database.

I hope I have been clear enough to describe what I am after.

I did have one question after your response, and that is, should I have my
Data Display application talking directly to the service for the data or is
it ok to have it talking directly to the database where the data is being
stored?  I have the flexibility to go either way at this stage and would
like to know that I'm designing applications in the best method as I will be
creating quite a few similar applications under the same architecture.

Thanks

"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message
news:4248a0b1$1@newsgroups.borland.com...
>
> "Daniel Stevenson" <d.stevenson@ocreage.com.au> wrote in message
> news:42489956@newsgroups.borland.com...
>
> > What is the best way of doing this?
>
> There are several different approaches to that, each one with its own
> advantages and disadvantages.  Which approach you use depends on what kind
> of data you want to send back and forth to/from the service, and also
> whether you want to do anything else with the service besides just
> configuration.  Please provide more details.
>
>
> Gambit
>
>