🚀 go-pugleaf

"Remy Lebeau [TeamB]" <gambit47_no_spam@yahoo_no_spam.com> wrote:
>
>"JD" <nospam@nospam.com> wrote:
>
>> I need to write a simple Client/Server application
>> where the client can accept messages initiated by
>> the server and send a message to the server that
>> requires a response from the server.
>
>What kind of messages exactly?

I know what I need but I don't know enough about how things
work to answer that question. All I want to do (at this point)
is prevent multiple clients from writing to the database at
the same time (which I know I don't *need* a server for) and
to use the server to notify (other) clients that the database
has changed.

There are other design considerations like distributed
processing and dial-up/web-based access but they're for
the future.

What kind of messages should I use?

>> Should I be looking at TServerSocket or Indy for this?
>
> [...] Either one can be used.

That's what I've been able to gather.

> The real question us - how much work are you willing to do yourself, 

Well, I hate to do more than I have to but in this case I've
decided against Indy because I need to learn and Indy will
make too much of it transparent to me. If it (the server) were
more complicated ... but it isn't.

~ JD