.NET Remoting

Communication is key at 1SEO.com when it comes to web development, so this is why we dabble with .NET Remoting. .NET Remoting is a Microsoft application programming interface for interprocess communication released over a decade ago with the 1.0 version of a .NET Framework. Like similar technologies such as CORBA and RMI, .NET Remoting is intricate, yet its fundamental nature is simple. With the assistance of an operating system and network agents, a client process sends a message to a server process and receives a reply.

In its most straightforward sense, .NET Remoting enables software components to network across application domains. The components interacting with each other can be in different processes and systems. This enables us to create n-tier distributed applications.

Now, what if for one reason or another we need to use a part of code located at a different application domain running within the same application located in a different process running on the same machine, or located inside another process running on a different machine? For uses like this, .NET Remoting exists.

Ultimately, .NET Remoting was created to provide a solution for problems that exist with the communication between application domains and processes. .NET Remoting solves these problems in a seamless and transparent way. This is due to the awesome power of the .NET Remoting programming model and the run time support.

.NET Remoting allows an application to make an object (termed a remotable object) available across remoting boundaries, which includes different appdomains, processes, or even different computers connected by a network. The .NET Remoting runtime hosts the listener for requests to the object in the appdomain of the server application. At the client end, any requests to the remotable object are proxied by the .NET Remoting runtime over Channel objects that encapsulate the actual transport mode, including TCP streams, HTTP streams, and named pipes. As a result, the .NET Remoting application can be made to support different communication protocols without recompiling the application.

1SEO.com's web developers are adept at using .NET Remoting. When Microsoft developers first designed the .NET Remoting structure, they took flexibility and customizability into consideration. .NET Remoting is dealt with easily by separating the remotable object (the object that you need to call, remotely located at another application domain or process) from the client, server application domain, or from any specific mechanism of communication. 1SEO.com will replace one communication protocol with a different one without the need to recompile the client or the server. Another flexibility related feature is that .NET Remoting is a language independent framework, we can choose any application mode to communicate from. Any application can host a remoting object providing services to any client whether or not it is located within the same process boundaries, or in separate processes located on one machine or a set of dissimilar machines.

Contact 1SEO.com today to hear more about .NET Remoting as well as the services we are educated in!

[Go Back]