dotnet distributed apps: Hi All,

I have a remoting server which will cater to the client request in
asynchronous way, and the number of clients can be any,in the
implemention of the remoting server ,i am spawning one thread for each
client request. the server does bit of work before sending the results
to client.

my concern regarding this is ,if for each request one thread is
spawn,then say if there are 26 clients requesting for the same servies
at the same time ,i belive there won't be any problem for 25 clients
(only 25 threads can be run in parallel(switched) in windows one
processor m/c),but the 26th client request will be queued and it has
to wait for the threads to free up.

in this implementation i am not using threadpool ,i am creating threads
by my self.

the problem that i presume is all the subsequent client requests after
25 will be queued,
so can any body suggest any alternative to this approach, bascially i
want the build a scalable system.

Hope i am clear.

Thanks in advance
Deepak

Deepak,

And another option is to put a compute grid behind your server. This will
give you a model that can scale to the thousands without bogging down the CPU
that the server is running on.

..NET Grid computing solutions:

Commercial-> Digipede Network (http://www.digipede.net/products/sdk.html)
Free Developer Edition available.

Open Source-> Alchemi (http://www.alchemi.net/)

Kim Greenlee

--
digipede - Many legs make light work.
Grid computing for the real world.
http://www.digipede.net
http://krgreenlee.blogspot.net

"deepak" <tsdeepak@gmail.com> wrote in news:1162552343.651743.233860
@e3g2000cwe.googlegroups.com:

[quoted text, click to view]

You should host your remoting objects in IIS - and use stateless remoting.