On Mon, 3 Apr 2006 01:00:02 -0700, Itay Sandbank wrote:

> Can someone please point me in the direction of a good document explaining
> how remoting works with threads? Which threads are used, can I limit these
> threads some way (I'd like, for instance, all calls made on a specific
> SingleCall objects to occur in a specific thread), etc... ?
>
> I'm also looking for some documented behavior regarding asynchronous
> calls, sinks and threads. Can I trust a single remoted method call to occur
> all in one thread in the server, or can it take place in two or more threads
> when asynchronous calls are made?

> AFAIK, in .NET Remoting, each remote invocation (regardless of whether the
> object accessed is a SingleCall or a singleton object) in done in its own
> thread (taken from the ThreadPool i think). In case of a singleton object,
> this means that you have to take care of protecting shared variable and
> synchronizing your code if necessary. So even if you have only one method
> exposed via .NET Remoting, each remote call to this method will occur in
> different threads.

On Mon, 3 Apr 2006 02:37:01 -0700, Itay Sandbank wrote:

>> AFAIK, in .NET Remoting, each remote invocation (regardless of whether the
>> object accessed is a SingleCall or a singleton object) in done in its own
>> thread (taken from the ThreadPool i think). In case of a singleton object,
>> this means that you have to take care of protecting shared variable and
>> synchronizing your code if necessary. So even if you have only one method
>> exposed via .NET Remoting, each remote call to this method will occur in
>> different threads.
>
> Yes, thanks, this far I already realized the first time I tried to write a
> remoting server, and threads started flying all over the place... But what
> happens in asynchronous calls when I write my own sink? Also, is there some
> sort of sink provider (or something else) that provides single-threaded
> calls? If not, I guess I can try to write one...