Hi Stuart, > Remoting > -------- > Has no native support for security/authentication unless you > use IIS as the host server (which will compromise performance > somewhat).
True, hosting in IIS drains the performance but nevertheless, using the BinaryFormatter via HTTPChannel (hosted in IIS) is faster than ASP.NET Web Services in most scenarios. [for the full comparison, please go to: http://www.dotnetremoting.cc/DotNetCentric/Articles/Remotingvs.ASP.NETWebSer v.asp] But nevertheless: If you aren't going to be .NET<->.NET (on client and server), you should stay away from Remoting as the RPC-Style SOAP encoding using by Remoting is way slower than the document style of ASP.NET Web Services. If you're only going .NET<->.NET Remoting is usually faster. just my 2c, -Ingo Author of "Advanced .NET Remoting" http://www.dotnetremoting.cc You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
