Messages can be thought of as a container for communicating data between co-operating, message sinks. These message sinks could be anywhere along the message sink chain: in the client sink chains or in the server sink chains. A message object is passed from message sink to message sink, through the chain and carries set of named properties such as, but not limited to, action identifiers, envoy information, and parameters.
An object that implements the interface IMessage meets the minimum qualification to be considered a message object. Also, there is no restriction that the exact object received by a message sink must be passed on to the next sink, though this will often be the case.
Although it is not a requirement that the objects in the property bag be serializable, it is certainly something that the message sink implementer would want to consider since an properties that need to flow out of the application domain will need to be serializable. Objects should also be agile if they are to be used in cross-context, same app-domain calls.
IMessage
[Visual Basic] Public Interface IMessage [C#] public interface IMessage [C++] public __gc __interface IMessage
[JScript] In JScript, you can use the interfaces in the NGWS frameworks, but you cannot define your own.
Class | Description |
---|---|
MethodCall | [To be supplied.] |
MethodResponse | [To be supplied.] |
ReturnMessage | This class implements IMethodReturnMessage which is used to return a message in response to a method call on an object at the end of the message sink. |
[To be supplied.]
Namespace: System.Runtime.Remoting
Assembly: mscorlib.dll