Re: wire stack words and diagram
Hugo Haas <[email protected]>
| Newsgroups | gmane.comp.web.services.ws-arch |
|---|---|
| Organization | World Wide Web Consortium (W3C) |
| Message-ID | <[email protected]> |
* Ugo Corda <[email protected]> [2002-10-01 09:18-0700] > >This has to be contrasted with other features (e.g. signature) > >that may leave outside the binding, e.g. expressed as SOAP header > >block(s). > > What if I had a Request-Response MEP and a MOM-based binding. In that case, > I would probably need to put the return address information in some header, > so that the receiving service can know where to send the (asynchronous) > answer back to. Would you consider that header to be part of the binding? According to the SOAP 1.2 specification[1], a feature expressed as a header is a SOAP module, and will be processed according to the SOAP processing model. Binding features, as I understand them, result from the carrying of the message with certain properties and do not show in the message. Request-response can be achieved via a module (e.g. specifying a reference and a reply address) or via a binding (e.g. using an HTTP request). Regards, Hugo 1. http://www.w3.org/TR/2002/WD-soap12-part1-20020626/#extensibility -- Hugo Haas - W3C mailto:[email protected] - http://www.w3.org/People/Hugo/