Re: Binding example discussion

On Wed, Jul 18, 2001 at 12:22:20PM +0100, Marc Hadley wrote:
> The candidate HTTP binding contains the following text:

Just to clarify, it isn't 'the' candidate.


> "correlation - HTTP provides implicit corellation between its request
> and response messages; SOAP applications may choose to infer corellation
> between the SOAP envelope transfered by the HTTP request and the SOAP
> envelope returned with the associated HTTP response."
> 
> I'm not sure that this is really rigorous enough to allow interop. What
> if the SOAP receiver (HTTP server) decides not to infer correlation and
> the SOAP sender (HTTP client) decides to infer correlation. Unless we
> have a means to allow the client and server to agree on on whether the
> response is correlated to the request then we have to specify it one way
> or the other - no ?

Well, this information certainly has to be somewhere; I don't know if
it should be in as 'low' a place as the binding definition, though.
There is a large amount of shared state between SOAP endpoints; the
basics should be reflected in the (relatively) unchanging
specifications; IMHO more application-specific things such as
communication-channel attributes need to be agreed upon by some other
mechanism (such as WSDL).


-- 
Mark Nottingham, Research Scientist
Akamai Technologies (San Mateo, CA USA)