Also, if you are concerned about security ?! :) Web Services ------------ Can be secured and clients authenticated using IIS mechanisms (NTLM, Basic, Certificates etc)
Remoting -------- Has no native support for security/authentication unless you use IIS as the host server (which will compromise performance somewhat). Cheers, Stu -----Original Message----- From: Thomas Tomiczek [mailto:[EMAIL PROTECTED]] Sent: 02 May 2002 15:53 To: [EMAIL PROTECTED] Subject: Re: remoting vs. web services This has already extensively been discussed. In partcular it loks like this: Web Services: * Limited functionality (no callbacks, object referenced etc.) * Bad performance * Big plus: works through ttp proxies. * Cross platform. Remoting: * .NET only. * full remote object implementation with object pointers, callbacks, events etc. * faster due to less overhead (no soap, binary format). Regards Thomas Tomiczek THONA Consulting Ltd. (Microsoft MVP C#/.NET) -----Original Message----- From: Bob Edwards [mailto:[EMAIL PROTECTED]] Sent: Donnerstag, 2. Mai 2002 16:50 To: [EMAIL PROTECTED] Subject: [DOTNET] remoting vs. web services Can you tell me the fundamental differences between Remoting and Web Services? Why would you prefer to use one over the other? Is one a sub-set of the other? Thank you. Bob You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
