Microsoft® .NET Remoting

Message Flows

Examining the message exchange between the JobClient and JobServer applications at various points of interaction can be quite instructive. Because we’ve chosen the HTTP channel with the default SOAP formatter, we can view the messages in a mostly human-readable form by using a tracing tool. Because the messages can be large, we’ll try to break some of them into chunks that are easier to explain.

The JobClient application instantiates a proxy to the JobServerImpl type when the application first starts. Because the application configures the JobServerImpl type as a well-known object, the client doesn’t need to send a message to the server application until the client application accesses the remote object instance in some way—for ...