Advantage of Remoting over Web Services - .Net Remoting

Advantage of Remoting over Web Services.

.NET Remoting allows objects to interact that can be hosted in different application domain within the same process or different process. The objects can also interact over intranet or internet. It supports many different protocols unlike Web Services that works over SOAP/HTTP protocol. .Net Remoting can work on TCP protocol that provides speed benefit from its counterpart.
Being tied up with IIS, .Net Web service can only work with producer /consumer model whereas .Net Remoting can share objects from any type of application. .Net Remoting being part of .Net Framework support full .Net type system and can expose any object to the client. .Net Web Service supports on those types that can be expressed with XSD.

When to use .Net Remoting over Web services?

.Net Remoting provides distributed solution for a corporate use. So, if you need distributed environment to be implemented for internal use, .Net remoting is the best choice. If you require a faster distributed solution, .Net Remoting with TCP protocal using binary format is faster than Web services. .Net Remoting is better solution when large transfer of data is required.
When should we choose .Net Remoting over .Net Web Services? - .Net Remoting
.Net Remoting provides distributed solution for a corporate use. So, if you need distributed environment to be implemented for internal use, .Net remoting is the best choice....
What are the ways to configure Remoting objects before client can use them? - .Net Remoting
.Net Remoting - There are two ways that the remoting objects can be configured....
Define Delegates and Events - .Net Remoting
.Net Remoting - A delegate acts like a strongly type function pointer.....
Post your comment