Hi Vikram, I think in most of the cases there will be no problem. However, remoting performance in concurrent environments is currently affected by the threadpool heuristics. If by some reason one of the machines is using 100% of the CPU you will have problems like the ones described in this thread:
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&threadm=%23ppaSB cgCHA.2248%40tkmsftngp11&rnum=1&prev=/groups%3Fq%3DStrong%2Bevidence:%2Bthre ading%2B%252B%2Bremoting%2Bnot%2Bworking%26hl%3Den%26lr%3D%26ie%3DUTF-8%26oe %3DUTF-8%26selm%3D%2523ppaSBcgCHA.2248%2540tkmsftngp11%26rnum%3D1 By using a cluster, i think that you will have a strong concurrent environment. and believe me that this issue can really jeopardize your application scalability! I've been told that this problem will be corrected in 1.1 final and only final version. Regards, Manuel ----- Original Message ----- From: "Vikram S" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, December 17, 2002 12:39 AM Subject: [ADVANCED-DOTNET] .NET Remoting In a Clustered Environment. > Hi, > > I am planning to use .NET Remoting for transfering data between client and > server in an asynchronous way. Since the application needs to be highly > available, we will be using a Win2k Cluster with fail-over. Are there any > issues in using .NET Remoting with any particular type of cluster ?? > > Thanks, > Vikram > > You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or > subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
