Hi, My application has one thread responsible for the total occupation of the cpu usage, but it is running with a low priority.
> That's correct behavior, you don't need to change it. I mean, if you have > 100% CPU usage, your other clients should wait. Letting them run would just > cause more contention for the CPU, making the whole thing slower. As soon as > previous calls finish, new clients will be serviced. > Correct?? All the remoting calls will be blocked, not just a few ones. I'm sure that this didn't happen with DCOM. At least i had never experienced something similar. I could expect an exception, they are really well design in the .net framework. Therefore, i think there is a problem with synchronization somewhere in one of the remoting classes. Remoting is well design, but this is not acceptable. Manuel You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
