[lnkForumImage]
TotalShareware - Download Free Software

Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

microsoft.public.dotnet.framework.remoting

System design: management of server side application threads

timasmith

7/29/2004 10:48:00 AM

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
1 Answer

Someone@yahoo.com

7/29/2004 7:12:00 PM

0

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


"Tim Smith" <timasmith@hotmail.com> wrote in message
news:a7234bb1.0407290247.7648ca37@posting.google.com...
> 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