web services and .net remoting

Question

when we use .net remoting and where web services?

Anuja Pawar · Answer

Hi Emmy The Web services technology enables cross-platform integration by using HTTP XML and SOAP for communication thereby enabling true business-to-business application integrations across firewalls. Because Web services rely on industry standards to expose application functionality on the Internet they are independent of programming language platform and device. Remoting is .a technology that allows programs and software components to interact across application domains processes and machine boundaries. This enables your applications to take advantage of remote resources in a networked environment. Both Web services and remoting support developing distributed applications and application integration but you need to consider how they differ before choosing one implementation over the other. In this article I will show the differences between these two technologies. I will present samples for each type of implementation and identify when to use which technology. .NET Remoting uses a flexible and extremely extensible architecture. Remoting uses the .NET concept of an Application Domain (AppDomain) to determine its activity. An AppDomain is an abstract construct for ensuring isolation of data and code but not having to rely on operating system specific concepts such as processes or threads. A process can contain multiple AppDomains but one AppDomain can only exist in exactly one process. If a call from program logic crosses an AppDomain boundary then .NET Remoting will come into place. An object is considered local if it resides in the same AppDomain as the caller. If the object is not in the same appdomain as the caller then it is considered remote. In .NET remoting the remote object is implemented in a class that derives from System.MarshalByRefObject . The MarshalByRefObject class provides the core foundation for enabling remote access of objects across application domains. A remote object is confined to the application domain where it is created. In .NET remoting a client doesn't call the methods directly; instead a proxy object is used to invoke methods on the remote object. Every public method that we define in the remote object class is available to be called from clients. For more details refer this good links http://www.codeproject.com/KB/WCF/WCF_Web_Service_Remoting.aspx http://msdn.microsoft.com/en-us/library/ms978411.aspx