One point, Remoting can work through fire walls, etc using http over port 80 as its transport.
The critical thing is whether you are talking .NET to .NET. if you are then remoting is probably a better solution, if you are not (or may not be) then WebServices are the way to go. Regards Richard http://staff.develop.com/richardb -----Original Message----- From: dotnet discussion [mailto:[EMAIL PROTECTED]]On Behalf Of Thomas Tomiczek Sent: 02 May 2002 15:53 To: [EMAIL PROTECTED] Subject: Re: [DOTNET] 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.
