🚀 go-pugleaf

"Deepak Mishra" <deepak.dmishra@gmail.com> wrote in message
news:41c03b9d$1@newsgroups.borland.com...

> 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).

Why won't it be started with the OS?  It should be.  Just don't have it
doing any actual work until requested.

> 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.

Have MyServer use TCP/IP to communicate back and forth with FTPService as
well.  When MyServer accepts a new client, send a request to FTPService to
begin working.  When all clients have disconnected, send a request to
FTPService to stop working.  Using TCP/IP, MyClient can also connect to
FTPService to make its own start/stop requests directly.

There is a difference between starting/stopping the service itself, and
having the service start/stop just its internal work.  Your descriptions so
far have suggested that you are trying to do the former.  You should do the
latter instead.

> 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).

You don't need it.  Just specify NULL to specify the local machine.  Don't
try to access the service object directly from remote machines.  Use TCP/IP
to communicate with the service instead.

> 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.

If you can, then use threads inside MyServer.  I see no reason why it needs
to be separated into its own service/process.  Unless you want the FTP work
to be performed while MyServer is not running, but it does not sound like
you do.  MyClient is already connected to MyServer anyway, so it can send
its start/stop requests to MyServer via the connection it already has.


Gambit