Call Context Message Flow

Call context data is piggybacked on a method call but isn't necessarily related to the specific method. In accordance, the .NET Remoting infrastructure sends our CallContextData object via the SOAP header rather than the SOAP Body element. Here's the response SOAP message for the DoExpensiveWork method call:

<SOAP-ENV:Header>

<h4:_CallContext href="#ref-3"

xmlns:h4="http://schemas.microsoft.com/ clr/soap/messageProperties" SOAP-ENC:root="1"> <a1:LogicalCallContext id="ref-3"

xmlns:al="http://schemas.microsoft.com/clr/ns/ System.Runtime.Remoting.Messaging"> <CurrentConnections href="#ref-6"/> </a1:LogicalCallContext> <a2:CallContextData id="ref-6"

xmlns:a2="http://schemas.microsoft.com/clr/nsassem/ LoadBalancing/DiscoveryServerLib%2C%20 Version%3D1.0.871.14847%2C%20Culture%3Dneutral%2C%20 PublicKeyToken%3Dnull"> <_CurrentConnections>1</_CurrentConnections> </a2:CallContextData> </SOAP-ENV:Header>

<SOAP-ENV:Body>

<i7:DoExpensiveOperationResponse id="ref-1"

xmlns:i7="http://schemas.microsoft.com/clr/nsassem/ LoadBalancing.IJobServer/LoadBalancingLib"> <return>true</return> </i7:DoExpensiveOperationResponse> </SOAP-ENV:Body>

0 0

Post a comment