Web Services v/s .NET Remoting

Web Services v/s .NET Remoting

• Fab5

  Hi HBOne,
  
  Here are some links which have the analysis that you need:
  
  Guidance on "How to Choose"
  http://msdn.microsoft.com/library/default.asp url=/library/en-us/dnbda/html/bdadotnetarch16.asp
  
  Performance Comparison: .NET Remoting vs. ASP.NET Web Services
  http://msdn.microsoft.com/library/default.asp url=/library/en-us/dnbda/html/bdadotnetarch14.asp
  
  Remoting Vs WebServices.
  http://www.thinktecture.com/Resources/Articles/REMOTINGVS.ASP.NETWEBSERV.html
  
  Also note that .NET Remoting is deprecated once Indigo is released:
  Is .NET Remoting Dead
  http://blogs.msdn.com/richardt/archive/2004/03/05/84771.aspx
  
  Regards,
  Vikram
  --------------------------------------------------
   Mark the reply as an answer if you found it helpful
  --------------------------------------------------
  
  

• Marque IV

  HI HBOne,
  
  In order to make sure you are writing an app that can be easily upgraded in future when Indigo arrives make sure you take a look at the following two blogs:
  http://blogs.msdn.com/richardt/archive/2004/03/05/84771.aspx
  http://blogs.msdn.com/mattavis/
  
  Regards,
  Vikram
  http://dotnetupdate.blogspot.com/
  
  

• Mr. Prez

  Yes there is a performance difference.
  Remoting in IIS can use binary format (not just SOAP).
  
  Some links on this:
  http://msdn.microsoft.com/library/default.asp url=/library/en-us/dnbda/html/bdadotnetarch14.asp
  http://www.thinktecture.com/Resources/Articles/REMOTINGVS.ASP.NETWEBSERV.html

  
  

• Leo8537

  Hi HBOne,

  In summary, according to me, if you are using microsoft techs on both the ends (provider and consumer) then go for remoting else go for web services. As both ends are microsoft centric in remoting, it provides some performance advantages as it can communicate in binary format while other communicates in SOAP.

  Keep an eye on WCF to make sure you get maximum out of your investment.

  Cheers,
  Kanaiya

  
  
  

• Petru66

  Hi,

  Additionally, you have remember that with .NET remoting you can levearge the usage of Generics (as part of .NET 2.0 Visual Studio 2005). Since the Generics are microsoft specific, these are not supported Web services.

  Once you are using generics, then .NET removing either tcp or http needs to binary and not soap driven.

  Regards,

  Ravi Vishnubhotla,

  Infosys Technologies Ltd.

  
  

• Yimin Wu

  I am trying a weird thing.

  Since web services transmits only certain data types, I am serializing an object into a stream and then converting it into Byte[]. This then is the return type of the web method. The consumer of this web service can deserialize the byte array provided it has dotnet on it.

  This way I am able to transfer custom objects over wire using web services and NOT remoting even when they are part of inheritance chains !. Object graphs are no hindrance this way.

  So why then does everybody talk of this limitation of web services

  Am I missing something

  
  
  

• Barry Harkness

  In terms of performance, is there a difference between .NET Remoting and Web Serviceswhen the latter is hosted by IIS. If I understand correctly, in this case they would both be using SOAP to communicate with their clients, and I would like to know if there will still be a performance difference.
  
  

• mike_n

  Could there be any valid reason to choose Web Services over Remoting when It is guaranteed that .NET would exist on both the client and the server(or on all tiers of an n-tier model)
  
  

• sergeyv

  Yes there is a big difference between the SOAP format used by Remoting and the SOAP format used by Web Service.  The SOAP format used by Remoting is very custom to MS, so do not try to connect non .NET application using Remoting SOAP format.
  
  ka

  
  
• Web Services v/s .NET Remoting