Menu
I know web service and have some knowledge on remoting. Both concepts invoke methods on the client machine so where lies the difference ??
Through remoting we can also execute the method on the remote machine and the same functionality can be achieved through web service too..
Please excuse me if it is the obvious question..
463
Remoting is a fancy word describing technologies that allow code in one process invokes a service (calls a remote procedure, or invokes a method on a remote object) in another process.
- XML Web services are more restricted than objects exposed over . NET Remoting. - XML Web services support open standards that target cross-platform use. - XML Web services are generally easier to create and due to the restricted nature of XML Web services, the design issues are simplified.
With . NET remoting, client applications can be built that use objects in other processes on the same computer or on any other computer that is reachable over its network. The . NET remoting framework can also be used to communicate with other application domains in the same process.
The . Net remoting infrastructure requires FullTrust permission to execute on either the client or the server. Due to the fact that FullTrust permission is required, Remoting endpoints should be authenticated and encrypted in order to protect the system and the data.
Both support distributed applications.
Web services are cross platform, using common standards and work through firewalls. They also think in terms of messages, not objects - you send a message to a service, and you get a reply.
Remoting is an MS only technology which is not cross platform and talks in a binary format. It thinks in terms of objects, you create an object on the remote server and work with it. It doesn't work well with firewalls. Remoting is also dead these days, MS favour WCF (which includes web services)
65
.NET Remoting concept is a Microsoft/.NET specific interprocess communication technology.
The term "Web service" is very diffuse due to its hype. But I think the W3C definition is intended in most cases. It defines the use of WSDL as interface description and SOAP as message protocol.
According to Microsoft .NET Remoting: A Technical Overview on MSDN, Remoting uses either a binary or XML encoding. Whereas the XML encoding uses SOAP. But as far as I know, it does not adhere to the WS-I Basic Profile. Hence, it provides an extremely limited Web service interoperability.
Both concepts allow interprocess communication. If your application only uses .NET, then using .NET Remoting is a good choice.
However, if you plan to provide interoperability with other programming languages than you should use Web services.
33
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
