2.1.3 SOAP Transport
At a high level, a Two-Way Remote Method invocation is modeled as a SOAP request message with an associated response message. A One-Way Remote Method invocation is modeled as a SOAP request message with no response message.
A request message MUST be constructed as follows:
The content of the request message MUST be a valid Envelope infoset per [SOAP1.1] section 4.
The SOAP body infoset MUST contain a valid method request struct per [SOAP1.1] section 7.
Any method parameters MUST be encoded as a valid serialization of the [SOAP1.1] section 5 encoding.
A response message MUST be constructed as follows:
The content of the response message MUST be a valid Envelope infoset per [SOAP1.1] section 4.
The SOAP body infoset MUST contain a valid method response struct per [SOAP1.1] section 7.
Any method parameters MUST be encoded as a valid serialization of the [SOAP1.1] section 5 encoding.
When using .NET Remoting over the SOAP protocol, .NET Remoting can be bound to HTTP or TCP.
For HTTP, .NET Remoting method invocation MUST be bound to an HTTP request/response pair per [SOAP1.1] section 6.
For TCP, see section 2.1.1 (raw TCP binding).