🚀 go-pugleaf

Bob Gonder wrote:

> Current:
> One application (99% console, 1% GUI because radio buttons are a pain
> in console mode).
> It runs their business (Customer records, Invoicing, A/R, etc.)
> Perhaps 10+ users, maybe 1 to 6 sessions(consoles) per user.
> Exe is 1 Mb, uses 4 when loaded, and may expand to 20+ under use.
> Standard DOS-style file i/o pulls lots of files off the server, then
> updates randomly (with proper multiuser locking, etc).
> Goal: reduce network usage. (VPN bandwidth seems to be rather small)

Lets see if I understand correct. There is a (server)computer somewhere
that has the datafiles and your exe file. Then there is an intranet
or even an internet and VPN is used. There can be 10+ users each with
their own computer. To start your program the user opens a console window
first. The application is then loaded from the server and started. Each
user can open up to 6 consolewindows each running an instance of your
exe. Each instance loads the same files from the server. It is possible
that at a certain moment up to 60 instances of your exe are running
somewhere.

> Proposed:
> Hack the user i/o out of the application.(easy)
> Put the user i/o in a new Client.
> Add a connection facilitator to connect clients with new instances of
> the hacked application on the server.

Will put comments in another reply later.

Hans.