Yazan
If you haven't read Ingo Rammer's book on remoting by all means you'll want
to get it.
What we found in our stress testing was that for a SAO object the
implementor only sees a single thread. The remoting framework handles the
connection/socket threads. Try as we might we could not swamp t
in both 1.0 and 1.1 if you have 1 Processor:
- method execution is serialized at server side
- you only have concurrency if the server thread associated with the
remote call gets into a sleeping stage.
to "solve" the problem you can dispatch the execution to a second thread
with QueueUs
Look at how ASP.NET works.
ASP.NET also has only a limited number of threads, and still it manages
to handl way more connnected clients.
The same principles apply with remoting.
Thomas Tomiczek
THONA Software & Consulting Ltd.
(Microsoft MVP C#/.NET
> -Original Message-
> From: Moderat
