What happens when the method is called in an object-oriented non-remote environment. Logically, when the object method is called, it is sent to the object, inform it to perform a function. To some extent, the message is sent to the object, and this message is configured by some values transmitted to that method as a parameter. The entry point address of the method is the destination address of the message. At very low levels, the caller should be pushed into the stack along with the address of the method along with the method, and then, the caller sets the application's instruction pointer to the entry point of the method, thereby calling the method. Because the caller and methods follow the call specification, the method knows how to get its parameters from the stack in the correct order. In fact, the stack plays the role of the communication transport layer between method calls, transmits a function parameter between the caller and the modified party and returns the result.
Packaging the information called in a message object is an object-oriented manner to abstract and model the concept of "method call as a message". The name, parameter, and related information of the message object transfer method are called by the calling party to other method of the called party. .NET Remoting uses such a scheme to interact between distributed objects. The message object encapsulates all methods calls, input parameters, constructor calls, method return values, output parameters, exceptions, and more.
The .NET Remoting Message Object Type package implements the system.runtime.remoting.Mestage.Runtime.Remoting.Mestage.Runtime.Remoting.MESSAGE.RUNTIME.Remoting.Message.IMestage interface and serves sequentially. IMessage defines an identity member of an iDictionary type named Properties. This dictionary saves the naming properties and values describing the various aspects of the modified method, which typically contains information such as the URI of the remote object, the name of the modified method, and the parameters of any method. When the .NET Remoting Infrastructure passes the message. Net Remoting boundary, it sequences the value in the dictionary. The .NET Remoting Infrastructure has derived a centralized message type from iMessage.
Note Keep in mind that only the instance of the serialized type can pass through the .NET Remoting boundary. Keep in mind that the .NET Remoting Infrastructure sequences the message object, so that it passes through the .NET Remoting boundary. This means that if any objects stored in the Properties dictionary of the message object can pass through the .NET Remoting boundary with the message, these objects must be serialized.
