In the past articles, we read about “Server Activated” remote objects. We also ran through separate article for Single Call and Singleton on the Server activated remote objects. In this post, we will try how to use the “Client activated” remote objects.
Before we go on Client Activated remote objects, we have to know what is activation and where the object lives. The clear fact whether it is server activated or client activated is that the remote object lives in the “Remote Pool” of the server. Client activation means, the client sets up the object on the server’s remote pool using the operator new in the client. So, if you are building up a class for the Client Activated Remote object, you have the power of using the overloaded constructors.
In this article, we will explore how one can use a delegate on the functions exposed by the remote objects. Also, we will see how do we call those remote object functions as synchronous and asynchronous. Basic knowledge on threading will help you catch this article in a better way but not a mandate.
In the previous articles, we saw Single-Call Remote Object and Singleton Remote Object. In this article, we will explore the usage of Generic Interface in the Remote Objects. First, we will explore how the server will register it and then move on to the client which consumes it. Generic Interface is a C# concept. But here we will explore that in Dotnet remoting context.
In the previous article, we saw about the server activated Single Call remote object. Also remember, each call to the server will create a new remote object in the ‘Single Call’ technique. In this article, we will see how the Singleton Remote Objects work.
‘Dotnet Remoting’ is a client and server based distributed object technology. In this article, we will make two applications. One is a Remote Server, and another one is a Client. First, we will complete the Server application and then carry out with the client. Here, we create Single Call remote. You will learn more about it in this article.