Ingo, If the server platform is not .NET are you saying that Java is faster, better, easier? I have built remoting applications that talk HTTP/SOAP with non-.NET servers and it seems to work fine.
Kevin Burton .NET Common Language Runtime Unleashed -----Original Message----- From: Ingo Rammer [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 02, 2002 10:57 AM To: [EMAIL PROTECTED] Subject: Re: [DOTNET] remoting vs. web services Hmm ... actually I guess it's more like this ;-) if (serverPlatform == ".NET") { if (clientPlatform == ".NET") { return "Remoting"; } else { return "ASP.NET Web Services"; } } else { return "You're talking 'bout Java here?"; } .NET Remoting and ASP.NET have the same degree of support for firewall-configurations. Even when using HTTP, you can go for the BinaryFormatter in Remoting which will be faster ... just my 2c, -Ingo Author of "Advanced .NET Remoting" http://www.dotnetremoting.cc > -----Original Message----- > From: Mathieu Rachlin [mailto:[EMAIL PROTECTED]] > Sent: Thursday, May 02, 2002 5:48 PM > To: [EMAIL PROTECTED] > Subject: Re: [DOTNET] remoting vs. web services > > > I think the idea is that you should use SOAP if you are > crossing a firewall. > > Therefore, > > If Firewall Then Use WebService > Else Use .NET Remoting > End If > > I could be wrong... but that's what I'm hearing.. > > - Mat > > -----Original Message----- > From: Wang, Yongjian [mailto:[EMAIL PROTECTED]] > Sent: Thursday, May 02, 2002 11:09 AM > To: [EMAIL PROTECTED] > Subject: Re: [DOTNET] remoting vs. web services > > > But what about the differences between remoting (with soap > over http) and > web services? > > > -----Original Message----- > > From: Thomas Tomiczek [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, May 02, 2002 10:53 AM > > 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. > > 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.
