>
>Using manipulation of the SOAP header has a disadvantage. It requires the client to setup the proper implementation in order to do so. Thus, we have to provide samples and support that aspect as well. This is something we would like to avoid. Samples are provided in Visual FoxPro thus someone who would like to use our Web Service from VBScript, for example, would have a rough time to make it work.
>

I think it should help a lot if the namespace of the header will be the same as the rest of the webservice (UniversalThread) instead of "tempuri.org".

From the VFP ClientHeaderHandler class:

IF loHeaderNode.baseName<>'SessionInfo' OR loHeaderNode.namespaceURI<>'http://tempuri.org/SessionInfoHeader'
   RETURN .F.
ENDIF

For what I have seen, using C# you can easily define a header named SessionInfo and add an attribute manually to the proxy to use the header.

What I dont understand in the UT webservice, is why the header is not define in the WSDL file. The samples in the .NET framework help that use header define it in the wsdl.


May be someone will jump in and help me understand how all this work...

:-)