🚀 go-pugleaf

Bob Gonder wrote:

>Remy Lebeau (TeamB) wrote:
>
>>That is best accomplished using a centralized server that all instances are
>>connected to.  Issue the command to the server, and let it re-issue the
>>command to all connected clients.  Also possibly wait for a response to know
>>that all instances acknowledged the command.

The original issue was resolved with UDP, but a new issue has arrived.

>A simple broadcast method would lessen the current problems, and
>Gigabit will do away with the bandwidth problem before I can get C/S
>stable.
>
>I will however, keep your recommend in mind should I change my mind...

Well, I guess I'm changing my mind....
A customer wants to run my app over a VPN, but sucking files through
that staw is too slow.

Considering a 3-part approach.

a) Simple Server Applet that sits and listens for UDP connect request
from client. When request comes in, CreateProcess on second part
(application) passing client IP.

b) Application that relies on Client for screen and keyboard io (TCP
xfer both ways.)

c) Client Keyboard/Video/Mouse functions TCPd to application running
on server. Barely more than a dumb terminal. (Though any GUI screens
would need to implement on Client, but only a very few of those
exist.)

Advantage:
	Application is already modular in KVM functions, so wrapping
them in TCP should be painless. And application would run as it does
today.

Disadvantage:
	Many copies of the application loaded into the server. Since
all calculations would be on the server instead of the user, it's
gotta slog the server.

Is that a generally acceptable method?

I figure you are going to tell me to combine a and b.
That would be fine if I knew how......
Without rewritting the whole thing, I'd need a seperate copy of most
of memory for each user/instance. I guess that would still be
CreateProcess() then.

If it was a service, would I then need to use CreateProcessAsUser() ?

Can I just take a console application, put it in the startup folder,
and call it a service, or are there special considerations?

Since all instances would now be running on a single machine, would
MapViewOfFile() reduce some of the memory/processing overhead?
(Instance 1 reads/maps file A, then instance 2 would get it for free?)