System design: management of server side application threads

  • Thread starter Thread starter Tim Smith
  • Start date Start date
T

Tim Smith

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
 
Hi, Tim Smith:
Mute about dotNet remoting. Your job task can be easily completed with
help of my SocketPro at www.udaparts.com in dotNet and C/C++. All of
requests and returns can be queued and batched. You can use one center
application to manage other applications either remotely or locally without
any problem at all.

--
Yuancai (Charlie) Ye

Fast and securely accessing all of remote data sources anywhere with
SocketPro using batch/queue, asynchrony and parallel computation with online
compressing

See 30 well-tested and real OLEDB examples

www.udaparts.com
 
Back
Top