Re: Looking for a design pattern

From: Phlip (phlip_cpp_at_yahoo.com)
Date: 07/29/04 

Date: Thu, 29 Jul 2004 12:28:39 GMT

Tim Smith wrote:

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

Why are the threads there? Are they part of the server's socket
architecture? Can you multiplex input events together?

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

I see an event-driven architecture where each event handler can do something
to its target object within an object model. Adding threads is causing you
the problem of then managing them. 

-- 
  Phlip
  http://industrialxp.org/community/bin/view/Main/TestFirstUserInterfaces