🚀 go-pugleaf

1) Suppose I've the set of machines.
   a) Machine A - Acting as the database server. On which the Server application say (say "MyServer") of my client-server architecture is installed and running.

   b) Machine B1, B2, B3, B4....and so on - Prsentation layer (say "MyClient") of client-server architecture is installed.

   c) Machine C - This has nothing to do with my application.

2) Machine A will also have a windows service (say "FTPService") running on it alongwith  MyServer. 

3) FPService will not start automatically when the OS starts ( which usually is not the case with the normal windows services. It will be in a pause mode).

4)Whenever, first MyClient from any of the client machines (B1, B2...) connects to the MyServer, FTPService should get started.

5) MyClient will have a button for stopping the FTPService if it is running and they want to stop it.

6) MyClient will also have a button to start the FTPService if it is not running ( which will be the case when some other or the same MyClient has stopped it).

7) Whenever the last connected MyClient disconnects with the MyServer, FTPService should get stopped.


8) I'm using TCP/IP to communicate between MyClient and MyServer and also to uplaod files from Machine A to Machine C, through FTPService.

9) Machine A and Machine B1, B2, B3.....etc. are part of a LAN.

10) The whole setup of applications (the application will be deployed at at various locations on N number of LANs)

Now my questions are:

1) How do I get to to know the name of the Machine A at design time, to use the "OpenSCManager". (Keeping in mind point 10 above).

2) What will be better, creating FTPService as a windows service for the above requirements. Or to create a separate thread or process in the MyServer application to do the job tobe done by FTPService.

Regards,

Deepak