soap using remoting vs soap using web services

[B. Deepak]

Soap using remoting vs soap using web services which will be faster and why?


Thanks in Advanced,
Deepak

 

[Josh Twist]

Potentially, soap over remoting *could* be the quickest compared to
soap over asmx web services - but there wouldn't be much in it and this
shouldn't form the basis of your decision.

MS's advice is that you should only really be using remoting to cross
an appdomain within a process - not for distributed computing as the
web services will be compatible with .NET 3.0s WCF framework.

Check this out to help you choose:
http://msdn.microsoft.com/webservices/choosing/default.aspx

Josh
http://www.thejoyofcode.com/

 

[Martin.Kunc]

Hello,
here is one big difference which should cause faster soap over remoting
and that is serialization. While SOAPoWS uses only standarized xsd
allowed types and this way is working with them, SoapOverRemoting uses
specialized (xml based), but proprietary serialization. This has
various pros and cons, for ex. you can with remoting serialize
IDictionary based types. At the other hand, you can use remoting only
on .NET to .NET environment compared to WS scenarios where you
potentially could consume/provide throught platforms.
You can try this using Xmlserialization (WS) and Soapserialization
(Remoting) serializers watching the results.
This also makes SoapORemoting faster.
cheers, Martin