.Net
Remoting Overview - Dec
29, 2009 at 15:33 PM by Nishant Kumar
.Net Remoting Overview
Distributed application is a set of
components distributed across network and work as if all the components are
there on the same computer. These components based technologies can be
developed using DCOM, CORBA, RMI etc. These technologies are good for intranet
environment.
Microsoft has provided suitable framework for developing distributed
application through .Net Remoting and Web Services. Remoting.net allows
components to interact across application domains, processes, and machine
boundaries. It enables your applications to take advantage of remote resources
in a networked environment.
Web Services are best suited when clients outside the firewall calling
components on the server over the Internet.
Remoting.Net is the best solution when clients and components are inside the
firewall. It requires the client to be built using .NET which means it can’t
work in heterogeneous environments.
.Net Remoting uses channels (HTTP and TCP channels) to transport messages to
and from remotable objects. The HTTP channel uses the SOAP protocol to
transport messages which means all messages are serialized to XML. The TCP
channel uses a binary stream to transport the messages.
.Net Remoting supports two activation modes: Singleton and SingleCall.
Singleton mode allows only one instance of an object at any time which means
all requests are serviced by the single instance. You can maintain state across
each request using this mode. SingleCall Mode creates a new instance of the
object for each client request and are stateless.
.NET Remoting when hosted with IIS, can use all the security features of
ASP.NET. But you need to implement your own security features for the
application if channel is hosted in the process other than aspnet_wp.exe.
|
