.NET Remoting and Web services - Remoting.NET

.NET Remoting and Web services.

Parameters.NET RemotingWeb Services
Protocol.NET remoting can be accessed over any protocol, including TCP, HTTP or SMTP..NET web services can be accessed only over HTTP.
PerformanceIt is fast.It is slow.
SecurityIt can be hosted either in IIS or in another container.It can be hosted in IIS, by default.
InteroperabilityIt requires the client can be built using .NET, enforcing homogeneous environment.Web services support heterogeneous environments which means client and remote object can be built in any platform.
ReliabilityIt needs to maintain security on its own if it's not hosted using IIS. When hosted in IIS, .Net remoting is also as reliable as web services..Net web services are hosted using IIS, they are reliable.
State ManagementIn .Net Remoting, Singleton objects can share state, whereas if you don’t need to maintain state, you can use Singlecall objects.Web services are a stateless in nature like web application. You need to use state mechanism to retain state. You can use the session or application object to maintain the state.
Name the distributed systems available apart from .Net Remoting - Remoting.NET
.Net Remoting - Distributed Computing Environment/Remote Procedure Calls (DEC/RPC)....
Define proxy in .NET Remoting. - Remoting.NET
.Net Remoting - Its a fake copy of the server object that resides on the client side and behaves as if it was the server.....
Post your comment