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
OTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, October 22, 2003 10:29 AM
Subject: [ADVANCED-DOTNET] .NET Remoting and thread pooling
> I have a windows service that acts as a .NET Remoting listener for
incoming
> requests from remote clients. I verified that the listener does ac
> From: Moderated discussion of advanced .NET topics.
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Diranieh, Yazan
> Sent: Mittwoch, 22. Oktober 2003 11:30
> To: [EMAIL PROTECTED]
> Subject: [ADVANCED-DOTNET] .NET Remoting and thread pooling
>
> I have a windows service that acts
I have a windows service that acts as a .NET Remoting listener for incoming
requests from remote clients. I verified that the listener does actually use
the thread pool to service client requests. Now, given the fact that there are
(by default) only 25 threads available in each CPU's thread pool, s
