In the previous article, we looked at writing into the message queue. We wrote separate messages and a class instance to it. In this brief article, we will see how we can read Message from the Microsoft Message Queue (MSMQ).
In this example, we will see how to configure and use configuration files for dot-net remoting. Here, we create config file for both server and client. These config file replaces the configuration done through code. This example uses the Singleton Remote server example and then replaces some code with configuration file.
In this article, we will learn how to use the ‘HTTP Channel’ as transmission protocol. Also, we will create the Metadata Proxy from this HTTP Remote Server deployed remote objects using the ‘SoapSuds’ command line utility. Then we will consume this DLL in a client application to talk to the remote object exposed by the HTTP Remote Server.
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.