Hi,

I have a system which comprises of a number of server side application
and services.  There is a thread per service or application and some
threads may also create their own application threads.

ServerApplication.exe
             ----------Controller Thread
                                           ---------App1
                       ---------App2
                       ---------App3
             ----------Subsystem1
             ----------Major Application2

AnotherApplication.exe
             ----------App4

Other than the executable processes I want a remote application to
communicate with all server's and stop, start or get a status of any
thread.

 
  -----------                   ------------
  |  Server  |          --------| ServerApp |
  ------------          |       |-----------|
  | Start()  |          |       | Run()     |
  | Stop()   |<|--------|       | Dispose() |
  | Status() |          |       -------------
  ------------          |
                        |       ------------
                        --------| Controller|
                        |       |-----------|
                        |       | Run()     |
                        |       | Dispose() |
                        |       -------------
                        |
                        |       ------------
                        --------| AnotherApp|
                                |-----------|
                                | Run()     |
                                | Dispose() |
                                -------------
                         

The thread which creates other threads I assume would only be able to
execute the three thread safe calls.  But does that thread have a
list, does it queue incoming commands, should I create an exposed
remote interface, or open a port to wait for commands?

Lots of decisions and I wonder if this has ALL been done before - does
anyone have experience?

thanks

Tim