[Home] [By Thread] [By Date] [Recent Entries]


John F Schlesinger wrote:
> 
>...
> 
> To do this, the adapters (end points) and the brokers (intermediaries)
> absolutely have to agree on a single envelope (this is how IBM's MQ
> works too). SOAP does exactly what is needed for this problem. The fact
> that it is cross-vendor, cross-language and cross-platform and supported
> by over 100 free toolkits and is a component of every major package (in
> plan), major application server (again, in plan) and tool is a huge win.

Could you outline which of the technical features of SOAP you use beyond
its ubiquity? Do you use the SOAP encoding? The RPC/HTTP binding?
Headers? mustUnderstand? What transports do you use? How much "just
works" and how much are you coding yourself?

 Paul Prescod

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member