views:

58

answers:

0

Hi :)

1) I've noticed that the netTCP binding uses SOAP as the envelope, which I think then it uses SOAP as a message protocol. How could I create my own SOAP message, send it through the netTCP and the other side understand it?

2)Today, our application creates the SOAP envelope from scratch putting the proper namespaces and body elements. With a simple http clint we simply call a service passing our created SOAP envelope. Aftwe a while, the response from the HTTP client comes and we get the SOAP message xml and extract the information that we want.

This way, our HTTP client recieves the serialized content and sends the request. In that way, we have the felixibility that if the server creates a new service, we simply create the proper soap envelope and make the request without needint a proxy.

Via webservice that is possible because I can "open" the soap message, and im not really sure how to reproduce that behavior with netTCP

Thanks