🚀 go-pugleaf

JD wrote:

> Currently, the only requirements for the server are tracking
> users as they log on and off and sending and receiving messages
> to the clients. 

What is the user of a server ? Clients use servers. Are not clients
the only users? Please elaborate.

 > Also, the client could be on a a non-networked
> system.

Then the client would be on the same computer as the server!?

> What's the 'best' (perhaps fastest/easiest) way to meet minimum
> requirements?

Please elaborate first. As the other said already:
TServerSocket/TClientSocket come to mind. The chat example
that comes with bcb is a -not to good- start.

> In the future, some processing may be moved to the server which
> would involve client data manipulation and fetching and saving
> data to and from disk.

Well that can never be a problem. Why would it ? Why would it
change anything ?

> Same question: What's the best/fastest/easiest way?
> How would this solution impact on the choice of the first?

Do not understand that it had influence.

> There has also been discussion of incorporating dialup and/or
> internet access in the future. Recommendations?

TServerSocket/TClientSocket are unaware of dial-up, network or loop-back.
You do not have to care for that. It's all done for you by the OS.

> I also don't understand how the server gets started on the
> server. Would an install package take care of that or what?

The possibilities of starting a server are the same as any other app.
What has installing to do with starting ?

You see: more questions than answers ;-)

Hans.